Cream of the Crop 12

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 12 / Cream of the Crop 12 (Part II) / Cream of the Crop 12 (Part II).iso / BBS / FDLOG122.ZIP / FDLOG.DOC < prev next >

Wrap

Text File | 1996-03-20 | 153.7 KB | 3,199 lines

╒════╤╤═════╕ ╤ │ │ │ │ │ │ │ │ ╞════ │ │ │ ╒═════╕ ╒═════╕ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ╘╛ ╘╧═════╛ ╘═════╛ ╘═════╛ ╘═════╡ │ │ ╘═════╛ FDLog Version 1.22, 20-Mar-96 (C) by Lothar Lindinger User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── Index ───── 1. Introduction............................................................ 4 1.1 Who uses FDLog....................................................... 5 2. Licence................................................................. 5 3. Registration............................................................ 6 4. User's manual........................................................... 6 4.1 Mailer Setup......................................................... 6 4.1.1 FrontDoor V2.x Setup............................................. 6 4.1.2 InterMail V2.x Setup............................................. 7 4.1.3 Xenia Mailer Setup............................................... 7 4.1.4 McMail Setup..................................................... 7 4.1.5 Binkley Setup.................................................... 8 4.1.6 T-Mail Setup..................................................... 8 4.1.7 FIPS Setup....................................................... 9 4.2 Limits............................................................... 9 4.3 FDLog usage and setup................................................ 9 4.3.1 FDLog command-line............................................... 9 4.3.2 Joker............................................................ 11 4.3.3 FDLog's .INI file................................................ 11 4.3.3.1 .INI file keywords........................................... 12 [LogFiles]......................................................... 12 [RPLogFiles]....................................................... 14 [Addresses]........................................................ 14 [ConnIncl]......................................................... 15 [ConnExcl]......................................................... 15 [MsgIncl].......................................................... 15 [MsgExcl].......................................................... 16 [NetmailTemplates]................................................. 16 [HighCost]......................................................... 17 [CostIncl##-High|Low].............................................. 17 [HighExcl]......................................................... 18 [CostExcl##]....................................................... 18 [Holidays]......................................................... 18 [CostTran]......................................................... 19 [ConnTime]......................................................... 20 [RemoteCost]....................................................... 20 [Cost]............................................................. 21 [SysOpCost]........................................................ 22 [EchoFiles]........................................................ 23 [DownLinks]........................................................ 23 [NodeLinking]...................................................... 24 [Freeze]........................................................... 24 [Magic]............................................................ 25 [Include].......................................................... 26 [TranxAddresses]................................................... 26 [Settings]......................................................... 26 Mailer=AUTO|frontdoor|intermail|xenia|mcmail|mcmail/binkley|..|.. 27 ReqProcessor=AUTO|rp|easyerp|easyerp/binkley..................... 27 UserLogPath=<Path>............................................... 27 SummaryLogPath=<Path>............................................ 27 NetMail=<Path>................................................... 27 StartDate=<Date>................................................. 27 EndDate=<Date>................................................... 27 SystemName=<Name>................................................ 27 ══════════════════════════════════════════════════════════════════════════════ Index Page 1 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── LastMonth=yes|NO................................................. 27 UserLogs=YES|no.................................................. 27 ActivityLog=YES|no............................................... 28 TimeUsageLog=YES|no.............................................. 28 HighRateLog=yes|NO............................................... 28 EchoMailLog=YES|no............................................... 28 EchoFileLog=YES|no............................................... 28 NodeByName=NO|yes................................................ 28 FilesBBS=yes|NO.................................................. 28 NetmailReport=yes|NO............................................. 29 CrashMail=yes|NO................................................. 29 NMLevel=<Level>.................................................. 29 RequestAble=yes|NO............................................... 29 HighCost=yes|NO.................................................. 29 ConnTime=yes|NO.................................................. 29 DownLinkCostReport=yes|NO........................................ 29 CostBasis=ECHOTRANSFER|AllTransfer............................... 30 MailBasis=ALL|Downlinked......................................... 30 StaticCost=<Num>................................................. 30 StaticMail=<Num>................................................. 30 SystemMail=<Num>................................................. 30 MinDownlinkCost=<Num>............................................ 31 Color=YES|no..................................................... 31 Display=FULL|infos|warnings|errors|none.......................... 31 DispLevels=<Levels>.............................................. 31 LogName=<Filename>............................................... 31 LogLevel=<full|INFOS|warnings|errors|none>....................... 31 LogLevels=<Levels>............................................... 31 ImpulseCost=<Cost>............................................... 32 UseImpulse=yes|NO................................................ 32 RealDuration=YES|no.............................................. 32 SortBy=none|NODE|name|calls...................................... 32 SortMode=ASCENDING|descending.................................... 33 UseRemoteCost=NO|yes............................................. 33 UseDataBase=NO|yes............................................... 33 DataBaseMayAge=NONE|<num> days|months|years...................... 33 MonthlyLogs=no|YES............................................... 33 YearlyLogs=no|YES................................................ 34 P..Path P..Log................................................... 34 Currency=<Currency>.............................................. 34 DeleteOldLogs=yes|NO............................................. 34 FlipName=yes|NO.................................................. 34 FREQsInUserLog=yes|NO............................................ 34 RequesterLog=yes|NO.............................................. 34 RequestLog=yes|NO................................................ 34 RescanSemaphore=<File>........................................... 35 SemaphoreMaxWait=<secs>.......................................... 35 DownloadCounter=<Spec>........................................... 35 UpdateCounters=yes|NO............................................ 35 CentsPerUnit=<Num>............................................... 35 AlwaysRemoteCost=NO|yes.......................................... 35 ExtendedInfo=YES|no.............................................. 35 FailedFREQs=NO|yes............................................... 35 DLCLeadingZeros=YES|no........................................... 35 ForceDLCLength=NO|yes............................................ 35 AllCallsLog=NO|yes............................................... 36 ══════════════════════════════════════════════════════════════════════════════ Index Page 2 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── RemoveMissing=YES|no............................................. 36 AddMissing=NO|yes................................................ 36 CostSeparationLog=NO|yes......................................... 36 AllCallsLogType=CONNECT|sysopname................................ 36 MyCountryCode=[<Code>]........................................... 36 UserLogType=CONNECT|address...................................... 37 BinkleyMagics=NO|yes............................................. 37 RunSemaphore=[<File>]............................................ 37 TranxLog=<Filename>.............................................. 37 TranxUpdServer=NO|yes............................................ 37 TranxMaxDiff=<mins>.............................................. 37 TranxNetmail=NO|yes.............................................. 37 TranxTemplate=<File>............................................. 37 DateJump=<mins>.................................................. 37 ErrorLogName=<File>.............................................. 38 ErrorLogLevels=<Levels>.......................................... 38 ErrorNetmail=NO|yes.............................................. 38 ErrorTemplate=<File>............................................. 38 5. Templates............................................................... 38 5.1 What is a template?.................................................. 39 5.2 Template-Types....................................................... 39 5.3 Line-Feeds in templates.............................................. 39 5.4 Template-Formating................................................... 40 5.5 Available Templates.................................................. 41 6. Updates................................................................. 46 7. Bug reports............................................................. 48 7.1 Known Bugs........................................................... 48 8. Suggestions............................................................. 48 9. Thanks.................................................................. 48 10. Trademarks, Copyrights................................................. 49 ══════════════════════════════════════════════════════════════════════════════ Index Page 3 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────────────────── 1. Introduction ────────────────────────────────────────────────────────────────────────────── FDLog is a new and powerful Log-Analyzer for FrontDoor V2.x, InterMail V2.x, Xenia Mailer, McMail, Binkley (DOS and OS/2), T-Mail and the Win95/NT Point Mailer FIPS. There are really a pretty lot of nice features and this documentation shows how to use those. Please take some time to study my words and you will see that FDLog is most powerful product for this purpose. FDLog is in continous development since autumn 1994 and I do not have plans that change this. And here we go with the main feature list of this version of FDLog: - Support of seven different mailer-systems, FrontDoor V2.x, InterMail V2.x, Xenia Mailer, McMail, Binkley, T-Mail and FIPS with auto-detection or manual selection - Support of external request-processors. Currently supported request- processors are the Prime External Request Processor RP and EasyERP with both logtypes. The logfile-type can be auto-detected or selected manually. - Intelligent time synchronization via the Tranx-lines. Also Netware-Servers can be synchronized. - Usage of database that you can keep your logfiles small - Schedulers (monthly/yearly) for reports and netmail writing - NodeLinking of nodes which call with different mail-AKAs - File-request analyzer with possibility to update the download-counter in a FILES.BBS filebase - Complete dynamic cost-calculation for downlinks - Cost calculation also for remote-systems via its phonenumber presented in the logfile or its net-address. - Calculation of costs either per minute, with the use of impulses, per second with an optional call-answer-cost, or with a fixed cost for the first x seconds and afterwards per minute/second/impulse - Cost translation for consideration of different rates during different times on different days. - Consideration of modem-handshaking duration - MultiLog processing for MultiLine systems - Informing of your up- and downlinks about transfer statistics with netmails, node qualifying system with optionial call-threshold and powerful template system. - MultiZone support with automatic AKA-matching ══════════════════════════════════════════════════════════════════════════════ Introduction Page 4 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── - Logfile for every user - Summary statistics, sortable by different sort criteria - Programmable time period for cost calculation and caller statistics - Intelligent FILES.BBS support of created statistics with configurable download-counter - Automatically posted netmails to the SysOp if problems are encountered (configurable) - Shared access of the mailer's logfile - Flexible but easy to setup configuration file - free Demo-Registration-Key valid for five weeks - nice look and feel - and last but not least a good and solid support ────────────────────────────────────────────────────────────────────────────── 1.1 Who uses FDLog ────────────────────────────────────────────────────────────────────────────── I've written FDLog for people who are interested in up/downlink costs and callers. As there is no setup-program with mouse-support or other games you should be familiar with your mailer (FD/IM/Xenia/McMail/Binkley/T-Mail/FIPS) and your operating system (DOS,OS/2,...). I think it's rather important to have a well-working programm with useful output than having a nice colour- and windowful user interface. The nicest user-interface is useless if the program crashes all the time or if there are no useful options. However, I've deactivated the powerful features in the non-registered version. Registration is not expensive at all if I add all hours I've been sitting in front of my screen and hacking code into my programmer's editor. It's your contribution in the form of registeration that keeps me going on. ────────────────────────────────────────────────────────────────────────────── 2. Licence ────────────────────────────────────────────────────────────────────────────── FDLog is ShareWare. You may test FDLog for 30 days, afterwards you have to register or remove the product. You may copy FDLog or make it accessable for download as long as the con- tents of the original archive are left intact and NO files (i.e. banners) are added or changed. Anything else, like putting this software on a Shareware- Collection CDROM or something like that, needs the permission of the author first! FDLog is provided 'as is', without warranty of any kind, neither expressed or implied. The author only guarantees that FDLog and the documentation occupy diskspace. In no event will the author be liable to you for any damages, including lost ══════════════════════════════════════════════════════════════════════════════ Who uses FDLog, Licence Page 5 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── profits, lost savings or other incidental or consequential damages arising out of the use of this program. Writing of netmail-reports, multi-logfile processing, modem-handshaking time calculation, impulse-calculation, advanced database functions, downlink cost reports and the /NOWAIT command-line switch are only available to registered users. ────────────────────────────────────────────────────────────────────────────── 3. Registration ────────────────────────────────────────────────────────────────────────────── FDLog works with a small registration keyfile. This keyfile must be placed in the directory where FDLog is to be found. For more information about registration and the registration fee please have a look into the file REGISTER.DOC. If you want to check out FDLog with all its powerful features, then request FDL_DEMO >>NOW<< at my system (refer to updates). If you do not want to call my system directly you can also send a netmail to my mailmanager which will deliver an UUENCODED key to you. Using both ways, you will get a special demo key valid for 5 weeks which will open all features. You will also have access to FDLog Beta versions with this demo key! I would strongly recommend to check out the latest Beta version of FDLog - this gives you the latest improvements and bugfixes! ────────────────────────────────────────────────────────────────────────────── 4. User's manual ────────────────────────────────────────────────────────────────────────────── This is the main part of this documentation. Here the configuration and usage of FDLog will be discussed. When you work this through you will see the power and flexibility of FDLog. I am sure that there are tons of misspellings in this documentation. If you encounter any spelling, grammatical or other error, please don't hesitate to tell me about that. ────────────────────────────────────────────────────────────────────────────── 4.1 Mailer Setup ────────────────────────────────────────────────────────────────────────────── FDLog currently supports seven different mailer-types; more are about to come soon upon request. ────────────────────────────────────────────────────────────────────────────── 4.1.1 FrontDoor V2.x Setup ────────────────────────────────────────────────────────────────────────────── FDLog gets all it's information out of FrontDoor's logfile. Therefore you have to tell FrontDoor to create a logfile. Enter a logfile filename in Global-> Filenames in FDSETUP and set the following in Mailer->Log to Yes: $ Accounting info * Sent/Rcvd files ~ Session information ══════════════════════════════════════════════════════════════════════════════ Registration, User's manual, Mailer Setup, FrontDoor V2.x Page 6 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ~ Remote system's info : Transaction info % Transfer messages = Modem responses With this setup FDLog gets enough information out of the logfile. Please make sure that the cost-information in FDNODE.CTL is set to the CORRECT costs at the CHEAP telephone-rate. The costs/minute during the EXPENSIVE hours is set in the FDLOG.INI file. ────────────────────────────────────────────────────────────────────────────── 4.1.2 InterMail V2.x Setup ────────────────────────────────────────────────────────────────────────────── Unfortunately I have to say that I have never seen InterMail neither at work nor some documentation of it. I've implemented InterMail support just be look- ing at its logfile. However, you will have to switch on the following log-levels: $ Accounting info * Sent/Rcvd files ~ Session information ~ Remote system's info ~ Inbound activites % Transfer messages = Modem responses Please make sure that your cost-setup of InterMail fits for your environment! ────────────────────────────────────────────────────────────────────────────── 4.1.3 Xenia Mailer Setup ────────────────────────────────────────────────────────────────────────────── With Xenia it's even worse than with InterMail. I've no idea how to set up Xenia Mailer in a way that it works with FDLog. Just switch on every loglevel that makes sense ;-) As there is NO internal cost handling in Xenia (as far as I know), FDLog uses the information in [Cost], [SysOpCost] and [RemoteCost] to calculate the costs. Refer to [Cost], [SysOpCost] and [RemoteCost] for more information on how to setup these costs. ────────────────────────────────────────────────────────────────────────────── 4.1.4 McMail Setup ────────────────────────────────────────────────────────────────────────────── I've implemented McMail support just on analyzing it's logfile. Anyway, mean- while I switched from FrontDoor to McMail so have more ideas about McMail ;-) You should switch on at least the following Log-Levels in McMail: - non vital but nice + normal messages ~ Serial commands # Special infos ══════════════════════════════════════════════════════════════════════════════ InterMail V2.x, Xenia, McMail Page 7 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── Please set up "Currency" in your McMail configuration as follows: Currency , . 1 0 McMail can create two different types of logfiles: One type looks similar to a Binkley logfile, and the other one looks somewhat similar to FrontDoor. You can select the type with the "ShortLog" statement in McMail's configfile. FDLog can process both types using auto-detection. Anyway, if you want to select manually: FDLog's logfiletype for the "ShortLog" is "McMail", and for the longer one "McMail/Binkley". McMail also has in internal cost-handling. Please set this up carefully; FDLog will use McMail's cost information for outbound calls. It is important, that you deactivate McMail's intelligence and set up cost per minute in COST.TBL. For Austria it should look similar to that in McMail 1.0g5 and up. Nahzone All BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB B,67,600 Inland_1 All BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB B,267,600 Inland_2 All BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB B,400,600 Ausland_1 All BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB B,600,600 Ausland_2 All BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB B,800,600 Ausland_3 All BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB B,1400,600 Ausland_4 All BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB B,2133,600 ^^^^ ^^^ 2133 units (Groschen) per impulse ───────┘ │ 60 seconds per impulse ───────────┘ For Germany I recommend to set CentsPerUnit=1000 and to set up all costs/min multiplied by factor 10, because there are no commas allowed and in the cost- setup and the loss of one comma cause a loss of accuarcy. McMail 1.0g5 and up also supports simple calculation of handshaking times. This has to be switched if you are using FDLog! Put/Change this line in your McMail configuration: CostTimeOffset 0 ────────────────────────────────────────────────────────────────────────────── 4.1.5 Binkley Setup ────────────────────────────────────────────────────────────────────────────── I've implemented Binkley support just on analyzing it's logfile. It's about the same with Xenia: Just switch on every log level that could make sense. Binkley also has an internal cost-handling. Please set this up carefully; FDLog will use Binkley's cost information for outbound calls. The costs MUST be set up here that they will be charged at the beginning of every minute. ────────────────────────────────────────────────────────────────────────────── 4.1.6 T-Mail Setup ────────────────────────────────────────────────────────────────────────────── I've implemented T-Mail support just on analyzing it's logfile. It's about the same with Xenia: Just switch on every log level that could make sense. As there is NO internal cost handling in T-Mail (as far as I know), FDLog uses ══════════════════════════════════════════════════════════════════════════════ Binkley, T-Mail Page 8 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── the information in [Cost], [SysOpCost] and [RemoteCost] to calculate the costs. Refer to [Cost], [SysOpCost] and [RemoteCost] for more information on how to setup these costs. Please note that updating of download-counters for file-requests is not possible because T-Mail does not put any paths into its logfile! ────────────────────────────────────────────────────────────────────────────── 4.1.7 FIPS Setup ────────────────────────────────────────────────────────────────────────────── In the current version of FIPS v0.91b you cannot change any loglevels because there aren't any. All you have to do is to activate the check-box in Setup->Logfile settings->Log MAILER output. If you have done this, FIPS will create a logfile called FIPSMAIL.LOG in its system directory. All you to do is to put the name of this logfile into FDLog's [LogFiles] section in the FDLOG.INI and that's it. As there is NO internal cost handling in FIPS, FDLog uses the information in [Cost], [SysOpCost] and [RemoteCost] to calculate the costs. Refer to [Cost], [SysOpCost] and [RemoteCost] for more information on how to setup these costs. Please note that the FIPS currently does not support any inbound calls and so FDLog does not support that either. An FDLog update will be released when FIPS is able to handle inbound calls. ────────────────────────────────────────────────────────────────────────────── 4.2 Limits ────────────────────────────────────────────────────────────────────────────── The number of different callers is limited to a maximum of 4096 or to the available memory. FDLog makes use of EMS memory and swaps to disk if there is not enough memory. Since V1.08 FDLog is able to open the mailer's logfile WHILE the mailer keeps on running. There is no need to freeze your mailer any more. Logfile-sharing works under Multitasking environments like OS/2, DESQview or Windows and on networks. ────────────────────────────────────────────────────────────────────────────── 4.3 FDLog usage and setup ────────────────────────────────────────────────────────────────────────────── This part will show you in detail how to use and setup FDLog. ────────────────────────────────────────────────────────────────────────────── 4.3.1 FDLog command-line ────────────────────────────────────────────────────────────────────────────── FDLog is already grown to a quite complex piece of software. There are two possibilities to control FDLog: You can specify a VERY LONG command line or use the more comfortable way with a .INI file. Using the .INI file also gives some advantages and offers all features of FDLog to you. To get some information about the command-line switches please start FDLog with the swith "/?" (i.e FDLog /?). For every ══════════════════════════════════════════════════════════════════════════════ FIPS, Limits, FDLog command-line Page 9 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── command-line switch there is an equivalent entry in the .INI file but not the other way round: You can only use all features of FDLog when using a .INI file! For more information about the command-line switches please consider the equivalent .INI file settings explained below. IMPORTANT: Settings in the .INI file OVERRIDE same settings on the command- line. If the [Freeze] section is set up correctly in FDLOG.INI you can use the command-line switch /FREEZE to freeze your mailer. When use are using this switch FDLog will only freeze the mailer but not process any logfiles! To unfreeze you can then use /UNFREEZE. If you are using this FDLog will not process any logfiles as well! FDLog will return errorlevel 0, if the mailer could be (un)freezed and errorlevel 5 if an error occured during the (un)freeze-procedure (i.e. SemaphoreMaxWait-timeout). The switches /NOPER and /ONLYPER can be used to control the processing of periodic logfiles. If /NOPER is specified, FDLog will never create periodic logfiles or summaries although it would be about time to create them. /ONLYPER goes to other way - if this parameter is specified FDLog will only create periodic logs and ONLY if it's time to create them. The switches /TODAY and /YESTERDAY can be used to create the logs and summaries of the current day or the day before. Please note that you have to comment the switches StartDate and EndDate in the configuration file (if used) otherwise they override the command-line parameter! The switch /TRANX gives you the possibility to synchronize the clock of your system to the clock of a specific remote-system. Within FidoNet there are several system which a DCF77 clock-receiver installed. Therefore the time of these systems will always be 100% correct. If one of your uplinks uses such a clock receiver or synchronizes with a system that uses a receiver you can use this feature and your system clock will always be fully up-to-date. You also do not have to care about daylight-saving. Just call your boss, have FDLog's tranx function installed and let FDLog change to clock for you. FDLog can also update the clock of the Default-Server if you are logged onto a NetWare fileserver. Please note that you must be a console-operator to update the clock of a NetWare fileserver. You can define a console-operator on NetWare 3.12 using SYSCON->Supervisor Options->File Server Concole Operators. You must have supervisor rights on the fileserver to define a console-operator. FDLog also has a security-machanism built in the timesync-procedure: If the clock of your uplink went "mad" and shows completely the wrong time, FDLog will not update your system clock but can write a netmail about the problem to you. To do this, you can specify the maximum time difference. If the difference of your system clock to the clock of time-server is greater than <TranxMaxDiff> minutes (you can set this in the [Settings] section of your .INI file) this security mechanism will protect you from a totally wrong clock. If you want to use this feature, you will have to set up the following keywords in your configuration file: Section [TranxAddresses]: Define the addresses of your time-servers. Section [Settings]: TranxLog=<Logfile>: Logfile to search for Tranx-Sessions. Use the environment variable (%task%) support to specify ══════════════════════════════════════════════════════════════════════════════ FIPS, Limits, FDLog command-line Page 10 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── different logs on multiline systems. TranxUpdServer=NO|yes: Update a Netware-Server as well? Please note that the user logged on MUST be a console operator. TranxMaxDiff=<mins>: Max. allowed time-difference to time-server to update your system/server clock. TranxNetmail=NO|yes: Write a netmail to the first address specified in [Addresses] if the time-difference to a time-server was too big? TranxTemplate=<File>: Template file to use for the netmail If you use this switch FDLog will NOT process any logfiles due to speed reasons. Just use FDLog /TRANX in your mail-import job. Do not delete or change the file FDLOG.TRX. Otherwise your clock might be set to a wrong time. Use /WAIT to enable the 10 seconds pause after FDLog has completed its work. In the unregistered version this 10 seconds break always will be present. ────────────────────────────────────────────────────────────────────────────── 4.3.2 Joker ────────────────────────────────────────────────────────────────────────────── FDLog can handle jokers. Jokers are ONLY allowed in entries where this is specified seperately! FDLog is supporting the following jokers: * Randon number (0-n) of random characters # One number (0-9) or the character # itself ? One random character Example: -------- 2:24##/* With this any address will be selected that is in zone 2 and has a four character net-number which starts with 24. ────────────────────────────────────────────────────────────────────────────── 4.3.3 FDLog's .INI file ────────────────────────────────────────────────────────────────────────────── The way with the .INI file is a quite comfortable one and I am not going to write a setup program for FDLog in the near future. The .INI file is similar to Microsoft (R) Windows (TM) .INI files. There is a section-identifier in brackets "[]" which specifies the kind of data below. You can use comments everywhere in this configuration file after writing a semicolon (;). You should place your .INI file in FDLog's directory. At startup, FDLog looks out for a config-file named FDLOG.INI in it's directory. Of course, you can specify another config- file using the /C switch (see usage displayed with "FDLog /?"). FDLog's .INI file supports environment variables and you can also make conditionals using environment variables. This shows how to use it: %env% - will be translated in the contents of the environment variable env %env=string% - the rest of the line will only be processed if the contents of ══════════════════════════════════════════════════════════════════════════════ Joker, .INI file Page 11 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── the environment variable env are equal to string %env#string% - the rest of the line will only be processed if the contents of the environment variable env are not equal to string %% - one single % Example: -------- TranxLog=M:\LOG\MCMLINE%TASK%.LOG %TASK% will be replaced by the contents of the environment variable TASK. Especially in this case this makes sense if want to run a timesync on a multi- line system. If you are using McMail I am sure that have seen this stuff before :-) ────────────────────────────────────────────────────────────────────────────── 4.3.3.1 .INI file keywords ────────────────────────────────────────────────────────────────────────────── By the time, the following keywords in the .INI file are supported by FDLog: ────────────────────────────────────────────────────────────────────────────── [LogFiles] ────────────────────────────────────────────────────────────────────────────── After this keyword you specify your mailer's input-logfiles. You can write down more than one logfile here. This is very useful when working with multiline systems. The logfile of your line 1 should be in first place, the logfile of line 2 in second place and so on. If you want to exclude a certain logfile from being processed use "-" in front of the filename. Further you can specify HISDN, InitCost or RealCost after the logfile. This defines that FDLog will use a special way of cost calculation when processing this logfile. HISDN fits the way ISDN lines are donated in Holland. There are no impulses but the cost will be calculated in seconds and some kind of "answer-cost" that appears when your remote systems picks up the call. InitCost is somewhat simi- lar to HISDN, but the answer-cost is already a cost for a fixed time, and after that time calculation will continue with usual impulses or minutes. This "answer-cost" will be specified in the [CostTran] section; see below. HISDN will be calculated as follows: After the remote system has picked up the line, the answer-cost will be charged immediately. After a certain time, every second will be charged. A small example will make it clear: Cost/min: 60 units, answer-cost: 10 units, typically for 0 seconds, so really just for answering. Connect with 5 seconds: 15 units (10 U answer + 5 U call) Connect with 1 minute : 70 units (10 U answer + 60 U call) The answer-cost and the answer-time is set up in the [CostTran] section in [] brackets after every cost/min value. Refer to [CostTran] for more inform- ation. InitCost will calculate as follows: ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 12 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── After the remote system has picked up the line, the answer-cost will be charged immediately. After a certain time, calculation will continue as usual in minutes or impulses. Another small example will make it clear as well: Cost/min: 60 units, answer-cost: 80 units for the first minute, 1 impulse costs 60 units (to make it easier) Connect with 5 seconds: 80 units (80 U answer + 0 U call (0s)) Connect with 70 seconds: 140 units (80 U answer + 60 U call (10s)) Connect with 140 seconds: 200 units (80 U answer +120 U call (80s)) The answer-cost and the answer-time is set up in the [CostTran] section in [] brackets after every cost/min value. Refer to [CostTran] for more inform- ation. The RealCost keyword tells FDLog that the costs in the logfile are for sure 100% correct and should not be changed in any way. This can currently only happen if you are using McMail and taking the cost of cFos to McMail's log- file (no "NoFosCharge" keyword in the McMail config). You have to ensure that the costs in McMail's logfile are really correct and that cFos really gets the cost from your phone company. In Austria and Germany is DISABLED at the phone- company per default and you have to PAY for this additional information! An- other very important thing is, that FDLog will also calcuate the Costs via [Cost], [SysOpCost] and [RemoteCost] of the remote-system. FDLog has to do this to get the "basic" cost to the system and to calculate all necessary information for the stuff like modem-handshaking costs and the cost- separation-log. Therefore you will NOT find the Mailer's original costs in the cost-separation-summary and the high-cost and handshaking parts of the different summaries. Anyway, FDLog will give you a warning message if the calculated costs differ from the costs in the mailer-logfile. MultiLog processing is only availabe to registered users! Example: -------- [LogFiles] M:\LOG\FDLINE1.LOG M:\LOG\FDLINE2.LOG M:\LOG\FDLINE3.LOG HISDN M:\LOG\MCMLINE4.LOG REALCOST Is this case, FDLog starts processing with the first logfile (FDLINE1.LOG) and after finishing, it switches to the next one (FDLINE2.LOG). For the logfile FDLINE3.LOG FDLog will use the way of calculation that is used in Holland for ISDN lines (cost/sec + answer-cost). The next logfile (MCMLINE4.LOG) is a McMail logfile and FDLog will take all outbound costs directly out of MCMLINE4.LOG (due to REALCOST). In the user's logs there is written some information on which line which activity was on. In the other logs of FDLog there is written how many lines have been used for the statistics. Please note that more logfile entries in [LogFiles] do NOT represent more logs of one line, but represent the different lines! ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 13 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────────────────── [RPLogFiles] ────────────────────────────────────────────────────────────────────────────── In this section you specify the logfiles of your external request-processor. Please note that this is not necessary when you are using a mailer that does not verbose file-requests in its own logfile. Mailer's that behave like that are for sure McMail<=1.0g4 and InterMail<=2.29g. FrontDoor always verboses file-requests, even when using an external request-processor, therefore you can forget about this section when using FrontDoor - just leave it blank. As I don't know exactly about Xenia, Binkley and T-Mail, just check it out ;-) Another very important thing is, that this feature only works together with UseDatabase=Yes (refer to [Settings]); otherwise this section will be ignored! Currently supported request-processors are The Prime External Request Pro- cessor RP (ReqProcessor=RP) and EasyERP with both logtypes (ReqProcessor=EasyERP or ReqProcessor=EasyERP/Binkley). Example: -------- [RPLogFiles] M:\LOG\RPLINE1.LOG M:\LOG\RPLINE2.LOG M:\LOG\RPLINE3.LOG FDLog first analyzes all mailer-logfiles and then starts with the request- processor-logs. When FDLog gets out an request of the RP-Logfile, it checks if there was a call during the time of the file-request on the specific line. If your logfiles are not somewhat incomplete or corrupted, FDLog can actually find the call for the file-request and put the request into the request-data- base. If FDLog can NOT find a call for the file-request the request will be ignored. Please note that more logfile entries in [RPLogFiles] DO NOT represent more logs of one line, but represent the different lines! ────────────────────────────────────────────────────────────────────────────── [Addresses] ────────────────────────────────────────────────────────────────────────────── Here you write down your own net-addresses. FDLog supports as many AKAs as your computer's memory can keep. The addresses written down here are used to prevent writing messages to yourself and to select the most suitable AKA for writing netmail statistics to your up/downlinks. Example: -------- [Addresses] 2:314/20 16:500/420 68:434/0 These are net-addresses of 3 different zones/nets. Let's say you are polling on 2:314/13, 16:500/102 and 68:310/0. When FDLog starts writing netmails, it always chooses the most suitable AKA. For the message to 2:314/13 FDLog uses 2:314/20, for the message to 16:500/102 FDLog uses 16:500/420 and for the ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 14 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── message to 68:310/0 FDLog uses AKA 68:434/0. This feature CANNOT be switched off. If you want to disable it you have to remove the AKAs here. ────────────────────────────────────────────────────────────────────────────── [ConnIncl] ────────────────────────────────────────────────────────────────────────────── FDLog only accepts calls from and to systems which are qualified in the [ConnIncl] section, all other calls will be completely ignored. However, all calls will be written into the database, although if the system is not qual- ified. With this function you can create all logs and reports just considering a specific range of callers (e.g. just for a certain zone). By default ALL system are qualified. Example: -------- [ConnIncl] 1:* 2:* 6:* This means that all systems in zone 1, 2 and 6 that had a connection to your system are listed in the reports. All other systems are not listed and the costs to these other systems are ignored. ────────────────────────────────────────────────────────────────────────────── [ConnExcl] ────────────────────────────────────────────────────────────────────────────── Here you can specify a list of systems which are being disqualified. All calls from/to these systems are being ignored even if this system has been qual- ified before. By default NO system is disqualified. Example: -------- [ConnIncl] * [ConnExcl] 68:* In this case all systems except EroNet systems (zone 68) are qualified - all calls from/to EroNet systems are being ignored. ────────────────────────────────────────────────────────────────────────────── [MsgIncl] ────────────────────────────────────────────────────────────────────────────── Before FDLog writes a netmail to any system, the system has to be qualified. Systems below this keyword are being qualified. Jokers in the netaddresses are ALLOWED. Default setting is *, which means that every system is qualified. Example: -------- [MsgIncl] ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 15 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── 2:31* 16:500/102 In this case every system which nodenumber starts with 2:31 and the node 16:500/102 are qualified. With these special numbers it means: everybody in Austria (every Node in Austria starts with 2:31) is qualified to receive a netmail message and the former ZyXELNet Host in Vienna (16:500/102) is also qualified. FDLog will NEVER create a netmail-message to somebody else - he will be skipped. ────────────────────────────────────────────────────────────────────────────── [MsgExcl] ────────────────────────────────────────────────────────────────────────────── Systems after this keyword are EXCLUDED from receiving netmail statistics created by FDLog. If a system has been qualified in [MsgIncl] but can also be found in [MsgEscl] it gets disqualified. That means that FDLog will NOT write a message to this system. Jokers (*) are allowed. Example: -------- [MsgIncl] 2:31* [MsgExcl] 2:314/13 In this case every system in Austria except 2:314/13 is qualified to receive netmail statistics by FDLog. This feature is very useful if a specific node DOES NOT want to receive any statistics. ────────────────────────────────────────────────────────────────────────────── [NetmailTempaltes] ────────────────────────────────────────────────────────────────────────────── Here you specify the template that should be used for the netmail-report to a certain system. The syntax is this section is: <NodeSpec> <TPL-File> NodeSpec may contain Jokers to select a range of nodes. If a certain node is not included is this list, the FDLog's internal template will be userd. If there is no path in the file-name FDLog will search the file in FDLog's systempath. For information about the templates refer to chapter 5. Example: -------- [NetmailTemplates] 2:31* GERMAN.TPL 2:24* GERMAN.TPL * ENGLISH.TPL With this GERMAN.TPL will be used for all nodes whose nodenumber starts with 2:31 or 2:24, so all Nodes in Austria or Germany. The template ENGLISH.TPL will be used for all other systems. ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 16 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────────────────── [HighCost] ────────────────────────────────────────────────────────────────────────────── This section is not supported any longer since version 1.20 of FDLog; it is replaced by [CostIncl##-High|Low]. ────────────────────────────────────────────────────────────────────────────── [CostIncl##-High|Low] ────────────────────────────────────────────────────────────────────────────── In this part you specify, during which times which rate has to be used. The rates have to be specified in the [CostTran] section. ## specifies the number of the rate in [CostTran] that should be used, High specifies, that this certain rate is an "expensive" rate; and Low specifies that it is a "cheap" rate. One line in this section has the following syntax: <Weekday/Date> <StartTime> "-" <EndTime> If you specify a date without year, the current year will be adopted. Examples: --------- [CostIncl1-High] Workday 8:00 - 18:00 [CostIncl2-Low] Saturday 0:00 - 24:00 [CostTran] "Local" 67 67 40 "Domestic 1" 267 400 200 ^ ^ ^ │ │ └─ valid for [CostIncl2-Low] │ └────── valid for [CostIncl1-High] └──────────────────── Name of this rate With this you specify that the first entry in [CostTran] will be used from Monday - Friday, 8:00 - 18:00 and the second entry will be valid for the whole Saturday. This means: The cost of a call with a basis-cost of 67 units/min will not be changed from Monday - Friday 8:00 - 18:00 but will bet set to 40 units/min on Saturdays. The cost of a call with a basis-cost of 267 units/min will be changed to 400 units/min from Monday - Friday 8:00 - 18:00, and to 200 units/min on Saturdays. Possible keywords for weekdays are: Mon(day) : Monday Tue(esday) : Tuesday Wed(nesday): Wednesday Thu(rsday) : Thursday Fri(day) : Friday Sat(urday) : Saturday Sun(day) : Sunday Wor(kday) : Workdays: Monday to Friday ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 17 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── Eve(ryday) : just every day: always Hol(iday) : holidays, as described in [Holidays]; refer to [Holidays] You only have to specify the first three letters of the keyword. Of course you can also specify the whole ones :-) ────────────────────────────────────────────────────────────────────────────── [HighExcl] ────────────────────────────────────────────────────────────────────────────── This section is not supported any longer since version 1.20 of FDLog; it is replaced by [CostExcl##]. ────────────────────────────────────────────────────────────────────────────── [CostExcl##] ────────────────────────────────────────────────────────────────────────────── In this section you specify, during which days an in [CostIncl##] defined rate has not to be used. In generic this will be on holidays. You can specify dates and weekdays here. ## gives the number of [CostIncl..] that this exclusion-set will work on. Example: -------- [CostExcl1] 8.12. 25.12. This means that on Dec 8th and on Dec 25th the in [CostIncl1..] specified cost-translation will not be used. Instead FDLog will use the basis-cost. Possible keywords for weekdays are as in [CostIncl..]: Mon(day) : Monday Tue(esday) : Tuesday Wed(nesday): Wednesday Thu(rsday) : Thursday Fri(day) : Friday Sat(urday) : Saturday Sun(day) : Sunday Wor(kday) : Workdays: Monday to Friday Eve(ryday) : just every day: always Hol(iday) : holidays, as described in [Holidays]; refer to [Holidays] You only have to specify the first three letters of the keyword. Of course you can also specify the whole ones :-) ────────────────────────────────────────────────────────────────────────────── [Holidays] ────────────────────────────────────────────────────────────────────────────── The sense of this section is quite easy: It helps you to defining a group of days that differ from the usual days in some way. The main reason, why I implemented that is the new cost structure for Germany 1996. They will have about 7 different costs during differnt parts of a workday. Usually a workday is from Monday to Friday, but on holidays have to be treated as the weekend. Therefore you would have to specify all holidays in all [CostExcl##] sections ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 18 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── for the workdays. As these will be about 7, you have have to specify the holi- days for 7 times in the configuration file. Now you specify the holidays ONCE in the [Holidays] section, and then just use the "Holiday" keyword in the [CostExcl##] section which is the same as specifying all entries of [Holidays] there. You may use dates and weekdays here, as in [CostIncl..] and [CostExcl##]. Example: -------- [CostIncl1-High] Workday 8:00 - 12:00 [CostExcl1] Holiday [Holidays] 01.01 01.11 02.11 25.12 This actives cost-translation for cost-block 1 everyday from Monday to Friday except the on 1-Jan, 1-Nov, 2-Nov and 25-Dec. Possible keywords for weekdays are: Mon(day) : Monday Tue(esday) : Tuesday Wed(nesday): Wednesday Thu(rsday) : Thursday Fri(day) : Friday Sat(urday) : Saturday Sun(day) : Sunday Wor(kday) : Workdays: Monday to Friday Eve(ryday) : just every day: always The Holiday keyword is not allowed in this section as it would lead to a recursive definition. You only have to specify the first three letters of the keyword. Of course you can also specify the whole ones :-) ────────────────────────────────────────────────────────────────────────────── [CostTran] ────────────────────────────────────────────────────────────────────────────── In this section you set how to change the basis-rate during different times. You can optinally specify the description for this rate at the beginning within two quotes ("). This description will again appear in the Cost- Separation-Summary. This first parameter is the basis-rate; in general this will be the night-rate or the cheap-rate. This basis-rate also has to be set up in the cost-control- file of your mailer (FDNODE.CTL...) as well as in [Cost], [SysOpCost] and [RemoteCost] that FDLog can detect and eventually translate it. The 2nd parameter specifies the cost for the times specified in [CostIncl1], the 3rd parameter specifies the cost for the times specified in [CostIncl2] and so on. Additionally to this you can set up the answer-cost and answer-time for HISDN ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 19 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── (Holland ISDN) or InitCost (this is used in Great Britain) in bracktes "[]" after a rate. The delimitor between answer-cost and answer is a ":". The first value in front of the ":" is the anwer-cost and the second value after the ":" is the answer-time. To learn more about answer-cost and answer-time refer to [LogFiles]. Example: -------- [CostTran] "Local" 67 [10:60] 67 [10:60] 67 [10:60] "Dom 1" 267 [20:30] 400 [30:30] 200 [15:30] "Dom 2" 400 [30:30] 533 [35:30] 347 [25:30] ^ ^ ^ ^ ^ ^ ^ │ │ │ │ │ │ └─ Answ.cost(25)/time(30) [CostIncl2..] │ │ │ │ │ └─────── Cost/min for [CostIncl2..] │ │ │ │ └───────────── Answ.cost(35)/time(30) [CostIncl1..] │ │ │ └─────────────────── Cost/min for [CostIncl1..] │ │ └───────────────────────── Answ.cost(30)/time(30) for base-rate │ └─────────────────────────────── Cost/min Base-rate │ (FDNODE.CTL, [Cost], [RemoteCost]..) └───────────────────────────────────── Description for this rate ────────────────────────────────────────────────────────────────────────────── [ConnTime] ────────────────────────────────────────────────────────────────────────────── FDLog offers the feature to calculate the costs caused by the time the modem needs for its handshaking process as well. Is this section you specify the approximate time your modem needs to connect at a specific speed. First write down the speed (or a part of the connection message), then a ":" and then the time the modem needs. Example: -------- [ConnTime] 2400: 8 14400: 12 This says, that your modem needs 8 seconds to build up a 2400bps connect and 12 secondes for a 14400bps connect. ────────────────────────────────────────────────────────────────────────────── [RemoteCost] ────────────────────────────────────────────────────────────────────────────── FDLog is able to calculate the costs a remote-system has when connecting to your system. Therefor it is necessary to specify what cost a certain system has. With this system it is possilbe that YOU inform your downlinks about the cost THEY had on your system. The usage of this section is very simple. Just write the remote-system's nodenumner (Joker * is allowed) and afterwards the cost in units. This part will look similiar to FrontDoor's FDNODE.CTL Cost entries. Please note that when FDLog has found the FIRST fitting nodenumber it takes the cost written afterwards. This means that you have to be specific at the beginning of this section and get common below. Please also make sure that ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 20 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── the cost information here is correct; [CostTran] will also use these costs for translating costs into high costs. If you are using Xenia, T-Mail, or FIPS, FDLog will use these entries for all calls (in and out). See also [Cost] and [SysOpCost]. Example: -------- [RemoteCost] 2:314/3 267 2:314/* 67 2:31* 400 2:* 600 1:* 800 * 2133 This means, that the cost for 2:314/3 ist 267 units per minute, all other systems in net 314 (except 314/3) have to pay 67 units per minute, every system which nodenumber starts with 2:31 has to pay 400 units per minute, every system in Zone 2 600 units per minute, systems in zone 1 800 units and all other systems 2133 units per minute. ────────────────────────────────────────────────────────────────────────────── [Cost] ────────────────────────────────────────────────────────────────────────────── This section is an addition for the [RemoteCost] section. Since V1.22ß-3 FDLog also processes the "Phone:" entries that are written into the logfiles. These "Phone:" entries usually show the phone-number of the remote-system. Some systems (i.e. undialable points) do not present their phone number; they just present "-Unpublished-". In this case, FDLog just tries to get the cost of this system by using [SysOpCost] and [RemoteCost]. These numbers usually get presented in different styles. Currently, FDLog can convert the following styles into the international format: Intl. Format: 43-732-611243 (like in nodelist) Candidaties: {+}43"-"|"/"|" "732"-"|"/"|" "611243 {+}0043"-"|"/"|" "732"-"|"/"|" "611243 {+}0732"-"|"/"|" "611243 * {+}: 0..n leading "+". "-"|"/"|" ": Either one of those * : only, if MyCountryCode=43 in FDLOG.INI If a phonenumber starts with 0, and the 2nd character is not zero, FDLog assumes that the caller has "forgotten" to put his international access-code in front of the number and replaced the 0 with the number defined in the setting MyCountryCode plus a "-". If there is NO number defined in MyCountryCode this conversion will NOT take place! Now, when FDLog can convert the number into the international format, you just import your FrontDoor cost-table (from FDNODE.CTL) to define the different cost-zones. The style of one entry in [Cost] has to look as follows: <Prefix> <Cost> ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 21 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── FDLog will stop comparing the Prefix with the phonenumber after the first match has been found! Therefore you have to be specific at the beginning and gerneric at the end of the cost-table. Please note that the length of this cost-table is limited to 4096 entries. If no match could be found in [Cost], FDLog will continue searching for a match in the [SysOpCost] and then in the [RemoteCost] section. Example 1: ---------- [Cost] 43-732 67 43-7223 267 43- 400 In this example the cost/min for callers, whose phone-number starts with 43-732 is 67, for callers with 43-7223 the cost/min is 267 and for all other callers, whose phonenumber starts with 43- the cost will be 400. Example 2: ---------- [Cost] 43- 400 43-732 67 43-7223 267 This example shows how you should NOT do it. In this case, the 2nd and 3rd entry is redundant, because, FDLog stops at first match. So, if the phone- number of the remote is 43-732, the first match will be on 43- and FDLog will the 400 as cost/min for this caller, which is certainly not desired! Please note that this feature does not work together with InterMail because InterMail does not write the "Phone:" entry into its logfile. ────────────────────────────────────────────────────────────────────────────── [SysOpCost] ────────────────────────────────────────────────────────────────────────────── This section is another addition for the [Cost] and [RemoteCost] sections, which is available since FDLog V1.22ß-4. The behavior of this section is similar to the [Cost] section, with the difference that the costs will be mapped to a specific name of a SysOp, not his telephone-number. Please note that always the whole name will be checked and has to match. This means i.e. that you set up cost/min for "Lothar Lindinger" to 400 units/min. But what for? This can make sense, if you do not map the remote-costs via [Cost] and the remote-system does not present his phone-number; or maybe you have not setup your [Cost] section. The process the look up the costs for a remote-system is the following. At first, FDLog will check in [Cost] for a matching number. If not match could be found there, FDLog will continue checking for a match of the Sysop-Name (not cAsE SeNsItIvE) in [SysOpCost]. If there was no match in [SysOpCost] as well, FDLog will try to find a match via the address in [RemoteCost]. The style of one entry in [SysOpCost] has to look as follows: ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 22 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── <SysOp_Name> <Cost> Spaces in the SysOp-Name are not allowed and have to be replaced by an under- score (_). You have to set up the basis-rate (this is always the first para- meter in the [CostTran] line) for the specific SysOp (same as in [Cost] and [RemoteCost]). Example: -------- [SysOpCost] Lothar_Lindinger 400 Gero_Dirk_Lachner 600 Peter_Eigner 67 This says that costs from/to the system of Lothar Lindinger is 400 Units/min, from/to Gero Dirk Lachner is 600 Units/min and finally the cost to Peter Eigner is 67 Units/min. ────────────────────────────────────────────────────────────────────────────── [EchoFiles] ────────────────────────────────────────────────────────────────────────────── FDLog is able to determine whether a file is a mail-packet, an ARCMail or an EchoFile. In some cases e.g. if no .TIC/.ZIC is sent FDLog cannot check whether a file is an EchoFile or not. In this section you can specify the directories where EchoFiles come out. This means if somebody requests a file out of these directories it gets included in the EchoFile-Transfer statistics. This part is also important for downlink-cost reports; requested files out of there directories count like EchoMail/EchoFile and are NOT free. Example: -------- [EchoFiles] M:\ECHOAREA This means that every file requested out of M:\ECHOAREA is an EchoFile and also processed as EchoFile; it will be included in the ECHOFILE report and it is not a free file when calculating downlinks cost-reports. ────────────────────────────────────────────────────────────────────────────── [DownLinks] ────────────────────────────────────────────────────────────────────────────── Here you specify the downlinks of your system, Jokers (*) are allowed. Every downlink will be included in the downlink-cost report. Example: -------- 2:314/20.* 2:314/14 This specifies that all Points of 2:314/20 and 2:314/14 are downlinks of your system and will be included in the downlink-cost report. They will have to share YOUR costs :-) ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 23 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────────────────── [NodeLinking] ────────────────────────────────────────────────────────────────────────────── In this section you link specific systems to one system. This is i.e. useful if you have links that connect with different Names/AKAs but that are the same. An entry in this section has to look as follows: <SysOp-Name> <Main-AKA> [<AKA1>] [<AKA2>] .. [<AKAn>] Short addresses that depend on the previous address are allowed. This means that 2:314/20 21 22 is the same as 2:314/20 2:314/21 2:314/22 If a system connects with one of the specified AKAs, FDLog will automatically convert it's nodenumber to the Main-AKA und will also set the specified SysOp-Name. Please use "_" instead of spaces, otherwise it would be inter- preted as AKA. Systems, to which another node has been linked (not only in setup but in reality) will be marked with a "+" in every summary statistic. Example: -------- [NodeLinking] Lothar_Lindinger 2:314/20 21 22 68:434/5 If a system connects with AKA 68:434/5 and the SysOp-Name "Fake", FDLog will set the address to 2:314/20 and the SysOp-Name to Lothar Lindinger for the further handling of this call. ────────────────────────────────────────────────────────────────────────────── [Freeze] ────────────────────────────────────────────────────────────────────────────── Here you specify how FDLog can freeze your mailer, that all open files get closed. This is usually only necessary on MultiLine systems to compile the nodelist or to shorten the logs. An entry in this section looks as follows: <Freeze-File> [<Frozen-File> [<Actice-File> [<Unfreeze-File>]]] What FDLog does, is the following: FDLog will create the Freeze-File in any case. If a Frozen-File is specified, FDLog will wait until this file appears. If there is also the Actice-File specified FDLog will only wait for the Frozen-File when the Actice-File can be found. The Unfreeze-File and the Freeze-File (if still present) will be deleted when the mailer should start working again. If this Unfreeze-file is not specified, the Freeze-File will be deleted to unfreeze the mailer. FrontDoor uses the same Freeze/Unfreeze file while McMail uses different ones. If you are using FrontDoor these 4 files are the following: FDFREEZE.<Line> FDFROZEN.<Line> FDACTICE.<Line> FDFREEZE.<Line> As the unfreeze-file is same as the freeze-file it can be omitted. That FDLog will not wait until XMas (i.e. if a mailer-task screwed up and the actice-file is still present) there is a TimeOut that can be set via SemaphoreMaxWait= in the [Settings] section. Use FDLog /FREEZE to freeze the mailer and FDLog /UNFREEZE to wake it up again. ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 24 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── FDLog will return errorlevel 0, if the mailer could be (un)freezed and errorlevel 5 if an error occured during the (un)freeze-procedure (i.e. SemaphoreMaxWait-timeout). Example 1: ---------- [Freeze] M:\FD\FDFREEZE.1 M:\FD\FDFROZEN.1 M:\FD\FDACTIVE.1 M:\FD\FDFREEZE.2 M:\FD\FDFROZEN.2 M:\FD\FDACTIVE.2 M:\FD\FDFREEZE.3 M:\FD\FDFROZEN.3 M:\FD\FDACTIVE.3 This an example how to freeze a 3-line FrontDoor system, whose semaphore path is in M:\FD. Example 2: ---------- [Freeze] M:\MCM\MCMHOLD.1 M:\MCM\MCMSLEEP.1 M:\MCM\MCMRUN.1 M:\MCM\MCMSLEEP.1 M:\MCM\MCMHOLD.2 M:\MCM\MCMSLEEP.2 M:\MCM\MCMRUN.2 M:\MCM\MCMSLEEP.2 M:\MCM\MCMHOLD.3 M:\MCM\MCMSLEEP.3 M:\MCM\MCMRUN.3 M:\MCM\MCMSLEEP.3 This an example how to freeze a 3-line McMail system, whose semaphore path is in M:\MCM. ────────────────────────────────────────────────────────────────────────────── [Magic] ────────────────────────────────────────────────────────────────────────────── Since V1.20 FDLog checks out every file-request in detail to determine weather the file-request failed or not and to find out the size of the requested file. As it is not possible to guess the response file of a magic-file request you have to specify your magic-lists here; don't put your magic-files here, but the magic-list! The style in this list is: <Magic> <Filename> {<Filename>} Mailers that are similar to Binkley usually use another format to define their magic files. These mailers save the request-paths as well as the magics in one single file. Magics differ from the other entries in this file as they always start with an "@" in front of the magicname. FDLog can also process these files. You have to set the switch BinkleyMagics in the section [Settings] to "Yes" if you want to use this format. This list then looks like this: @<Magic> <Filename> {<Filename>} Expample: --------- [Magic] M:\FD\ALIAS.FD In this case FDLog reads and checks all magics defined in ALIAS.FD and will use them to analyze a possible Magic-file-request. ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 25 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────────────────── [Include] ────────────────────────────────────────────────────────────────────────────── In this section you can specify additional configuration files that should be processed. These configuarions do not need to be complete; it is enough if there is at least one section in this file. Including a file has the same effect, as if the contents of the included file would be located at the end of the calling file. You may use [Include] as well in files that have been imported themselves. You can specify up to 4096 files to be included, where every file has be written into one single line. Example: -------- Let's say you have a configuration REMOTE.INI (see below) that should be imported into the main configuration. All you have to do, is the following in the main configuration: [Include] REMOTE.INI The file REMOTE.INI can look i.e. like this: [RemoteCost] 2:* 600 1:* 800 * 1400 ────────────────────────────────────────────────────────────────────────────── [TranxAddresses] ────────────────────────────────────────────────────────────────────────────── In this section you specify your Time-Servers for use with the FDLog /TRANX functin. If you want to learn about the time-synchronization refer to the command-line switches, chapter 4.3.1. A Time-Server is specified via its fidonet-style address. If FDLog finds a call to a system that is listed in [TranxAddresses] after the last tranx session, your system clock will be synchronized with this system. A maximum of 4096 addresses may be listed in this session. Example: -------- [TranxAddresses] 2:314/13 This defines that 2:314/13 is a Time-Server and that you want to sychronize your time with the time of 2:314/13 when running FDLog /TRANX. ────────────────────────────────────────────────────────────────────────────── [Settings] ────────────────────────────────────────────────────────────────────────────── In this part all settings can be done. Settings in the .INI file override the same settings from the command-line. In the following I will list and explain the settings that can be done to FDLog. Default values are written in BIG letters. ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 26 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── Mailer=AUTO|frontdoor: Here you tell FDLog which type of mailer you are |intermail running. With AUTO FDLog tries to detect the type of |xenia|mcmail mailer you are using. There is NO command-line switch |mcmail/binkley for this option! |binkley|t-mail |fips ReqProcessor=AUTO|rp: Here you tell FDLog which type of request-processor |easyerp you are running. With AUTO FDLog tries to detect the |easyerp/binkley request-processor you are using. There is NO command- line switch for this option! UserLogPath=<Path>: The path where the user's logs are being stored. The equivalent command-line switch is "/D<Path>". Default: current directory SummaryLogPath=<Path>: The path where the summary logs are being stored. The equivalent command-line switch is "/V<Path>". Default: current directory NetMail=<Path>: The directory where to store the created netmail messages. This should be your mailer's netmail folder directory in *.MSG format usually. The equivalent command-line switch is "/F<Path>". StartDate=<Date>: The first day that is being analyzed in the logfile. Default: 1st of current month. The equivalent command- line switch is "/B<Date>". EndDate=<Date>: The last day that is being analyzed in the logfile. Default: last day of current month or if a start-date has been specified, last day of start-date's month. The equivalent command-line switch is "/E<Date>". SystemName=<Name>: The name of your System. In the .INI file it is allowed to use spaces, in the command-line NOT. Hovever, you can use _ instead of spaces in the command-line AND in the .INI file. Default: Taurus Alpha 1 (my system). The equivalent command-line switch is "/N<System_Name>". LastMonth=yes|NO: When you set this switch to YES FDLog creates the user's logs and statistics of last month's activity. This switch is useful when start FDLog automatically on the 1st of every month and you want FDLog to create all user's logs and statistics of the month that just passed by... Instead of LastMonth you can also use the much more powerful periodic functions, which will be explained later on. The equivalent command-line switch is "/L". If you specify begin- and end-date AFTER the LastMonth statement, LastMonth will be overridden. UserLogs=YES|no: Do you want to create a seperate logfile for every user that called your system. In this logfile the activity of this user is listed in detail. The name of the file depends on the user's node-number and the SysOp's name. ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 27 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── The first 4 letters are the 4 letter's of the SysOp's name. About the following number I only want to say that is are calculated of the nodenumber, but not more, because of security reasons. Otherwise you could possibly request the UserLog of anybody you know and that's not the way of living! The equivalent command line switch is "/U". ActivityLog=YES|no: Do you want FDLog to create a logfile where all in/out- bound activities of every user is listed. The created file is named ACTIVITY.LOG in the SummaryLogPath. The equivalent command-line switch is "/A". TimeUsageLog=YES|no: The time-usage log is similar to the activity log, but instead of the amount of data transfer the used time is being written down here. The created file is named TIMUSAGE.LOG in the SummaryLogPath. The equivalent command-line switch is "/T". HighRateLog=yes|NO: The high-rate log shows in- and outbound activities of all nodes with time and connection-length, and extra- costs caused by the high-rates during selected hours. Make sure that the switch HighCost is set to YES (see below). The name of the file created in the SummaryLog Directory will be HIGHRATE.LOG. There is NO command- line switch for this option! This logfile is avaiable to reg'd users only! EchoMailLog=YES|no: The EchoMail log shows the EchoMail-transfer in com- parsion to the total transfers. All Net- and Echo- mailpackets transferred are included in this log. The report will be created as ECHOMAIL.LOG in the SummaryLogPath. There is no command-line switch for this option. EchoFileLog=YES|no: The EchoFile log shows the EchoFile-transfer in com- parison to the total transfers. All files ending with .?<I|0-9|>C or which have been transferred from/to the directories specified in [EchoFiles] are included in this log. The Report will be created as ECHOFILE.LOG in the SummaryLogPath. There is no command-line switch for this option. NodeByName=NO|yes: You can use this feature, if you have up/downlinks which connect with different AKAs. If this switch is set to YES all calls from a specific SysOp (name!!) are being linked together; the nodenumber is irrelevant. Systems, to which another system has been linked, are marked with a "+" in every summary stat- istics. Section [NodeLinking] is much more powerful than this option. I recommend to use [NodeLinking] if you want to link nodes together. There is no command-line switch for this option. FilesBBS=yes|NO: Do you want FDLog to create a SuperBBS/QBBS-style FILES.BBS in the directory where the log/summary files ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 28 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── are stored. The equivalent command-line switch is "/W". NetmailReport=yes|NO: Do you want FDLog to create netmail-messages to the users that connected to your system. A netmail-message will only be written to systems that have been qual- ified with [MsgIncl]/[MsgExcl]. This feature is only available to reg'd users of FDLog. The equivalent command line switch is "/M". CrashMail=yes|NO: Should the created netmail-message be crash-mail? The equivalent command-line switch is "/Q". NMLevel=<Level>: <Level> is a numeric value >=1 that specifies a minimum number of calls (in- and outbound together) a node must have before he gets a NetMail sent from FDLog. It's not very useful to send a connection-report netmail to a system that has called your system just once for mail-routing. There is no command-line parameter for this option. RequestAble=yes|NO: Are the eventually created user logs filerequestable for the users that called your system? If you set this switch to yes, in the netmail to the user will be written that he can request his detailed user log. Be sure to have your request processer properly in- stalled and set-up before setting this switch to yes. The equivalent command-line switch is "/R". HighCost=yes|NO: This switch switches on cost translating depending on the settings in [CostTran], [HighCost] and [HighExcl]. All costs will be translated to the costs specified in [CostTran], dependig on the length of a call in a period specified in [HighRate] and wheter the date of call is included in [HighExcl] or not. Cost-Translating is only available to registered users! There is NO command-line switch for this option! ConnTime=yes|NO: Consider the time the modem used for handshaking or not. If this switch is set to YES, costs will probably rise due to the time the modem needed for handshaking. Make sure you set the settings in [ConnTime] properly. This switch is only available to registered users! There is NO command-line switch for this option! DownLinkCostReport=yes|NO: This is a great feature. I will have to explain that in detail to you. Many SysOps run their Node private and they have to pay for all the costs such a system causes. These costs will be mainly telephone- costs during the longer run. Now many SysOps have points and other downlinks who have to pay for the stuff the receive. This money is then usually used for keeping the system going. This is nothing against FIDO policy, but if a node gets MORE money out of this, that means that he MAKES money and this the FIDO-rules say that this is NOT allowed. Well, what to do now? On the one hand the SysOp needs the money for his system and ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 29 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── on the other hand he must not take to much. Some SysOps just have fixed "link-costs" per month or a fixed rate per MB, but this not "state-of-the-art". The best would be if all downlinks keep the uplink-system running and this calculation should be dynamically. And this is the point where FDLog comes in. FDLog is able to calculate the running-costs of a system very accurate and to link these costs to the downlinks. If you set this switch to Yes, FDLog will calculate the downlink-cost in a very transparent way for every downlink listed in [DownLinks]. More about this calculation in the ex- plaination of the next switch. The name of the created report will be "DOWNLINK.LOG". And, that I don't forget it but I think you could guess: This feature is only available to registered users! CostsBasis=ECHOTRANSFER:When calculating the costs for a downlink-system FDLog |AllTransfer has to calculate your own costs first. With this switch you can specify if you want all your cost (incl. File- Requests of some rubbish) linked to your downlinks or if you just want to link the amount caused by the link of the EchoMails and EchoFiles (see [EchoFiles]!!) MailBasis=ALL: FDLog always calculates a fixed cost per MB for the |Downlinked downlinks. But now there are two possibilities: Do you want, that ALL cost is to be paid by your downlinks in any case, then select "Downlinked". So, if you have cost of i.e. 1000 ATS caused by importing your Echo- Stuff and just ONE downlink who imports just 1% of all you import, he will have to pay ALL of your cost; and I'm sure he won't. So "Downlinked" is a very useful option if you have several downlinkes and a lot of mail is "downlinked". The other way is using "All". Here FDLog takes your outbound costs (set up with CostBasis), and devides this by the amount of received mail. Now you get YOUR cost per MB. Then you have to divide this cost/MB by the number of your downlinks and you get a new cost/MB for your downlinks. This method maybe is more fair to your downlinks, but you will only get all money back if EVERY downlink has odered ANY stuff you import. Use this, if you import most for yourself, and not for the downlinks :-) StaticCost=<Num>: This fix amount of money is being added to your out- bound costs. You can use this to cover your electricity bill for instance, or if you have extra payment to your uplink. This amount is understood per month! StaticMail=<Num>: You can use this switch to add some virtual extra- export to your downlinks. He will have to pay for this amount of mail although he never received it :-) You can for instance declare this as "BBS-Usage-fee". This amount is understood per month! SystemMail=<Num>: This amount of mail (in bytes) will be added to the mail-pool for calculating the cost per MN. You can set ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 30 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── set the amount of mail here that's just for your system and that the downlinks don't have to pay for. This amount is understood per month! MinDownlinkCost=<Num>: Here you set the minimum amount of money a downlink has to pay. If he his link costs exceed this minimum cost he will have to pay the actual link costs, otherwise the minimum cost. This amount is understood per month! Color=YES|no: If your computer is equipped with a colour graphics adapter and a monochrome monitor it can be possilble that you cannot read FDLog's status messages any more. In this case, set this switch to NO and all messages will be displayed in black/white. The equivalent command-line switch is /P. Display=FULL|infos With this setting you can set a level when FDLog makes |warnings outputs to the screen. With FULL every activity will |errors|none be displayed, with infos just useful status information, with warnings only warnings and erros, with errors only errors and with none there will be no screen-writes at all. This option is only available to registered users! The equivalent command-line switch is /O<Level>. Since V1.22 this keyword is obsolete but is still supported. The replacement for this switch is DispLevels=<Levels>. DispLevels=<Levels>: Similar to Display= you can adjust here what kind of information will be displayed on the screen. FDLog features the following levels: - (green) : Trivial/debug information + (green) : Informative stuff # (cyan) : Disqualification (Call/Netmail/...) ? (yellow): Warning - something might be wrong ! (red) : Fatal error - program will terminate All you have to do is to write the desired loglevels after DispLevels=. I.e. to see all messages you have to write "DispLevels=-+#?!". LogName=<Filename>: The output-logfile of FDLog. If no filename is speci- fied no logfile will created. There is NO command-line switch for this option! LogLevel=full|INFOS With this setting you can set a level when FDLog makes |warnings an entry into it's logfile. The levels are same as in |errors|none "Display=...". There is NO command-line switch for this option! Since V1.22 this keyword is obsolete but is still supported. The replacement for this switch is LogLevels=<Levels>. LogLevels=<Levels>: Similar to DisplayLevels= you can adjust here what kind of information should be logged to the logfile. FDLog features the following levels: - (green) : Trivial/debug information + (green) : Informative stuff ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 31 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── # (cyan) : Disqualification (Call/Netmail/...) ? (yellow): Warning - something might be wrong ! (red) : Fatal error - program will terminate All you have to do is to write the desired loglevels after LogLevels=. I.e. to see all messages you have to write "LogLevels=-+#?!". ImpulseCost=<Cost>: FrontDoor always calculates the costs per minute while your telephone company usually uses impulses to calc- ulate the costs. The cost of one impulse ALWAYS stays the same whereever you phone to but the time-difference between two impulses change in dependency of the cost per minute. For instance in Austria one impulse costs 0.80 ATS per minute. If you are phoning in your own city an impulse will occur approximately every 72 seconds - but when you phone to Germany there will be an impulse every 12 seconds. With this setting you specify the cost of ONE impulse of your telephone company. The default entry for this setting is 80; this is suitable for Austria. To say it once again in other words (this time for Germany with a local call): When the remote picks up the phone, there will be the first impulse and 23 Pfennigs are accounted. The next impulse will come exactly 6 minutes after the first one. This means, that a call with 3 minutes costs ex- actly the same as a call with 5 minutes and 55 seconds. After 6 minutes the 2nd impulse will appear. In a table this will look like this: Minutes from - to: 00:00:00 - 00:05:59 = 23 Pfennigs = 1 impulse 00:06:00 - 00:11:59 = 46 Pfennigs = 2 impulses 00:12:00 - 00:17:59 = 69 Pfennigs = 3 impulses There is NO command-line switch for this setting! UseImpulse=yes|NO: If you set this switch to YES FDLog will not use the entries in the logfile for cost-calculation but will recalculate FrontDoor's cost entry using the in- formation of the "ImpulseCost=" setting. The advantage of this method is that the cost will be much more acc- urate to the real-cost than FrontDoor's cost entry. Be sure that you've entered the correct "ImpulseCost" before using this feature! This great feature is only avaiable to registeres users! There is NO command-line switch for this option! RealDuration=YES|no: If this switch is set to yes FDLog writes information about the first and last call into the summary logs and the NetMail report. In the NetMail report the first and last call of the current user will be written. SortBy=none|NODE|name: The entries in the summary logfiles will be sorted by |calls one of these criteria. Secondary key is always the node- |duration|cost number (i.e. if there are some systems with just one |transfer call and you've set "SortBy=Calls" all systems with one ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 32 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── call be sorted by nodenumber). SortMode=ASCENDING: This setting specifies if the sort criteria sorts |descending ascending or descending. UseRemoteCost=NO|yes: With this setting you can tell FDLog whether if it should use the entries in [Cost], [SysOpCost] and [RemoteCost] to calculate the remote system's cost or set all inbound costs to 0. Please ensure that [Cost], [SysOpCost] and [RemoteCost] is setup properly before enabling this feature. If this switch is set to yes ALL inbound costs will have a * afterwards to indicate that is the cost of the remote-system, not your's. Please use this feature - it can be VERY interesting for your up- and downlinks. UseDataBase=NO|yes: If you set this switch to Yes FDLog will first scan all input logfiles if there are any calls which are not already in the database. If there are calls found, FDLog will add them to the database. All output log- files will be made out of this database which offers much faster access and more possibilities. Further it is not necessary to keep the big logfiles if you want to create reports out of them - every neccessary will be stored in this database and size of the database is about 10 times smaller than the one of the logfile. Enabling this switch also enables the scheduler to create Monthly/Yearly reports. After FDLog has pro- cessed your input logfile(s) once you can delete them without loss of any important information. If you want to create logfiles out of the database just for a specific line, disable the other lines with a "-" in front of their logfilenames in [LogFiles]. This feature and the resulting features are only available to registered users! DataBaseMaxAge=NONE|: This switch makes it possible that FDLog's database <num> days|months| doesn't grow too large. FDLog will remove all calls years older than the specified value on startup. Please note that deleted calls CANNOT be undeleted any more. They will be lost FOR EVER. FDLog always takes the first of the current month and calculates back the specified amount. So, if we have the November 7th now and you have set up "DataBaseMaxAge=1 Month" every call before October 1st will be deleted. If you use "year" FDLog calculates the years back from January 1st of the curr- ent year. If you think about that you will realize that "12 Months" and "1 Year" is NOT the same in this case. If you want to calculate the "yearly" reports, I re- commend using "1 Year" here at least. With days, FDLog calculates back the given number of days from today to delete the old entries, with None there in no maximum age for any entries in the database. MonthlyLogs=no|YES: If this switch is set to Yes FDLog's internal sched- uler will create all selected reports (see below) of ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 33 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── the previous month on the first run in the new month. With this switch you are always informed what happened the month before. The extension of the created reports will be Number of Month (2 chars) and the last number of the year. So .064 is a report of June 1994 (or 1984 or 2004, or...). This feature only works when using the database. YearlyLogs=no|YES: With this switch you can tell FDLog's internal sched- uler to create a complete year report of the year that just passed by. The logs will only be created on the first run in the new year. Please make sure that you have set DataBaseMaxAge to at least 1 Year to use this feature; otherwise the created reports will not be the complete summary of the last year. The extension of the created files will be the last two digits of the year these reports are valid for. This feature is only avail able when using the database. PUserLogPath,: These switches are equivalent to the ones without the PSummaryLogPath, leading "p"s. These switches specify the reports to PUserLogs, create (and where to create) when FDLog's internal PActivityLog, scheduler starts up. Only automatic Monthly and Yearly PTimeUsageLog, reports are affected by these switches. Please have PHighRateLog, a look the equivalent ones without the "p" to check PNetMailReport, out the meaning. By default, all switches are set to PEchoMailLog, NO and the path are the current directory. PEchoFileLog, PDownLinkCostReport, PRequesterLog, PRequestLog, PAllCallsLog, PCostSeparationLog Currency=<Currency>: The string defined here is used by FDLog to tell the the user (you and your up/downlink) in which currency the written cost is. It appears in any logfile as well as in the netmail-report. DeleteOldLogs=yes|NO: Delete all .LOG files in UserLogPath/SummaryLogPath on startup. FlipName=yes|NO: If you set this switch to yes, FDLog flips the name and code of the user's log. I.e. if the name of the user's log would be LOTH0815, it will be 0815LOTH if this switch is set to yes. This is to prevent FREQs of foreign userlogs. FREQsInUserLog=yes|NO: Include file-requests in user's logs? RequesterLog=yes|NO: Do you want FDLog to create a log where all Requesters are listed with their file-requests? RequestLog=yes|NO: Do you want FDLog to create a log containing all file- requests in alphabetic order? ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 34 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── RescanSemaphore=<File>:FDLog creates this file (if a filename is specified) after writing netmail messages. It is usually only used on multiline-systems to force the mailer to rescan the netmail folder. SemaphoreMaxWait=<secs>:Here you specify the max. time, FDLog waits for for a semaphore answer-file. This is currently only used for [Freeze]. DownloadCounter=<Spec>:Here specify the style of the download-counter. The first character is the start-character, the last char- acter is the end-character and the created download- counter will be as long as specified here. It does not matter which character you use inside this spec - it just represents the number of digits. So, i.e. [##] (this is default) will create a download-counter looking "[00]", <dddd> will create a download-counter looking "<0000>" or {x} will create a download-counter looking "{0}". If you just write DownloadCounter= FDLog will not create any download counters. UpdateCounters=yes|NO: When this switch is set to yes and also UseDataBase is set to yes (and only then) FDLog will increment the download counter of the requested file when writing it into the file-request database. So, this means, if you delete FDLog's database and FDLog enters this file- request into the database again it will AGAIN update the download counter! CentsPerUnit=<Num>: Here you can specify, how many "Cents" are equal one currency-unit. All cost-statements must be in Cents, commas are not allowed! The default for this switch is 100. This switch is mainly interesting, if the cost per minute is i.e. 0.014 currency units. In this case, set 14 Cents per minute and set CentsPerUnit to 1000. AlwaysRemoteCost=NO|: If you set this switch to Yes, FDLog will calculate the yes cost of ALL calls (so In- AND Outbound) out of [Cost]/ [SysOpCost] and [RemoteCost]. Usually FDLog takes the cost out of the mailer-logfile (except Xenia and T-Mail) to calculate the basiscost. This can be useful, if you have set up the internal cost-handler either wrong or not at all. ExtendedInfo=YES|no: If this switch is set to Yes, FDLog will write some information about date, time and line of any call to the screen/logfile. This reduces processing speed a little! FailedFREQs=NO|yes: With this switch you can setup whether FDLog should write failed file-requests into the reports or not. DLCLeadingZeros=YES|: Do you want to see leading zeros (Yes) or leading no spaces (No) in your Download-Counter? ForceDLCLength=NO|yes: If this switch is set to "No", and a download-counter ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 35 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── does not fit in the with DownloadCounter=[##] speci- fied length, FDLog will expand the field if necess- ary. If it is set to "Yes", FDLog forces the specified length and sets to counter to the possible maximum if it would not fit into the field. AllCallsLog=NO|yes: If you set this switch to "Yes", FDLog will create a file called "ALLCALLS.LOG" in the SummaryLogPath. This summary contains information about Line, Date, Time, Duration, Connect, Remote-System, Costs and File- Requests (see also FailedFREQs). RemoveMissing=YES|no: If this switch is set to Yes, FDLog will remove all entries from FILES.BBS where the corresponding file cannot be located. If this entry has a long description it will be removed as well. FDLog does only touch FILES.BBS in a directory, if - FilesBBS=YES is set in [Settings] - there are FDLog User or Summary logs in that dir- ectory - there was a filerequest out of that directory and UpdateCounters is set to Yes in [Settings] AddMissing=NO|yes: If this switch is set to yes, FDLog will adopt a file into FILES.BBS if it was requested but could be located in FILES.BBS. CostSeparationLog=NO|yes: If you set this swich to yes, FDLog will create a so called cost-separation summary. In this report all cost-zones defined in [CostTran] will be listed as as well as the different cost-blocks. So, if you want a very good report please be sure that you have all different rates defined in [CostTran]. Look into this summary, it's a very interesting one! AllCallsLogType=CONNECT: If you set this swich to "Connect", FDLog will put |sysopname the connect-string of every call into the Allcalls-Log. If you set it to "Sysopname", FDLog will replace the connect-string with the name of the sysop of the remote-system. MyCountryCode=[<Code>]:Here you can specify your own country-code (Austria=43, Germany=49, Great Britain=44, ...) if you want FDLog to convert local phonenumbers (ONE leading zero) into the international format. If you use the [Cost] section to get the cost of the calling system, you will usually set this up with international phonenumbers. If FDLog now encounters a phone-number that has only one lead- ing zero it assumes that the remote-SysOp has "for- gotten" to set up the phonenumber in the international and replaces the 0 with this CountryCode plus a "-". If you do not define any CountryCode or you comment this line, FDLog will not convert such a number. Plaese note that this conversion takes place BEFORE the call info gets written into the database due to speed- ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 36 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── reasons! Therefore a later change does not affect any calls already in the database! UserLogType=CONNECT: Here you can select what you want to see in the User's |address log. If you select CONNECT, the modem connect string will be written to the user's log, with address the main-address of the remote-system will be written here. Address can be interesting if you use NodeByName=Yes or [NodeLinking] but you want to know which line was actually online. BinkleyMagics=NO|yes: If you set this switch to Yes, FDLog will think that your magic-lists are in Binkley-Style. Therefore an "@" has to be placed in front of every magic name in the list. Only set this switch to Yes, if you really using this kind of lists! Refer to [Magic] for additional information. RunSemaphore=[<File>]: If you specify a file after this keyword, FDLog will create this file and delete it after completion. This can be helpful if you install some kind of "watchdog" on your system. If you have further questions about that please contact Peter Eigner, 2:314/13. By default no external run-semaphore will be created! TranxLog=<Logfile>: Logfile to search for Tranx-Sessions. Use the environment variable (%task%) support to specify different logs on multiline systems. To learn more about time-synchronization with a time-server please refer to the explanation of the /TRANX command line switch. TranxUpdServer=NO|yes: Update a Netware-Server on timesync sessions as well? Please note that the user logged on MUST be a console operator. TranxMaxDiff=<mins>: Max. allowed time-difference to time-server to update your system/server clock. If the difference is greater than the specified value, your system/server clock will not be updated but you will get a netmail instead if TranxNetmail is set to Yes. TranxNetmail=NO|yes: Write a netmail to the first address specified in [Addresses] if the time-difference to a time-server was too big? TranxTemplate=<File>: Template file to use for the netmail. Study the included template files and chapter 5 if you want to learn more about that. DateJump=<mins>: This keyword is only important if you are running McMail with ShortLog or FIPS. The problem is that especially McMail with ShortLog does write the date only upon startup. If your mailer never exits, there will be no date information any more. Therefore FDLog has to detect time-jumps in the log to keep the correct ══════════════════════════════════════════════════════════════════════════════ .INI file keywords Page 37 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── date. Usually a date-jump occurs if a new time is lower than the old time (i.e. from 23:50:20 to 0:02:30 or from 08:30:23 to 07:50:12) But what if you are running an automated DCF77 and daylight-saving changes? The clock might get set back and there is no datechange. With DateJump you can set the minimum time-difference between the two times that FDLog changes it internal date. Default is 120 minutes. That means that the new time has to be at least two hours lower than the old time that FDLog changes date. ErrorLogName=<File>: Here you set the name of FDLog's error logfile. FDLog will always create (NOT append) this logfile if there appeared messages listed in ErrorLogLevels. The main reason for this logfile is, that you can view when and where FDLog had some problems. Further this logfile can be included into the run-error netmail report. ErrorLogLevels=<Levels>:Here you can adjust what kind of information sould be logged into the error-logfile. FDLog features the following levels: - (green) : Trivial/debug information + (green) : Informative stuff # (cyan) : Disqualification (Call/Netmail/...) ? (yellow): Warning - something might be wrong ! (red) : Fatal error - program will terminate All you have to do is to write the desired loglevels after ErrorLogLevels=. I.e. to log warnings and errors you have to write "ErrorLogLevels=?!". ErrorNetmail=NO|yes: If you set this switch to yes, FDLog will write a netmail the first address specified in [Addresses] when entries have been made to the error-logfile during the run of FDLog. ErrorTemplate=<File>: Template file to use for the netmail above. Study the included template files and chapter 5 if you want to learn more about that. Well, that's it for so far. I suggest you should try the possibilities of FDLog. I am sure you will like it and find it useful. If you need help, connect FDLog's support echo "FDLOG.SUP" or write a netmail to me. I know that not everything is easy to understand, but try and check it out. And, if come accross something really strange please feel free to tell me about that. ────────────────────────────────────────────────────────────────────────────── 5. Templates ────────────────────────────────────────────────────────────────────────────── FDLog has a very powerful template-system for writing netmails. Different templates can be used for mails to different nodes; refer to [NetmailTemplates] for additional information about this. ══════════════════════════════════════════════════════════════════════════════ Templates Page 38 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────────────────── 5.1 What is a template? ────────────────────────────────────────────────────────────────────────────── To explain it in easy words: Every template will be exchanged by a certain string; it's some kind of a variable. I.e. the template "@PROGRAM@" will be exchanged by "FDLog V1.xx", where xx is the current version of FDLog. In FDLog a template will always be written within two "@". If you are using a template in a template, you will have to write the inner template within two "%". If you are still putting a template in there, it has to be written within two "~". More then 3 levels are currently not supported. ────────────────────────────────────────────────────────────────────────────── 5.2 Template-Types ────────────────────────────────────────────────────────────────────────────── In FDLog there are three different types of templates: Macro-Templates (M): The template will be exchanged by a certain string. I.e. "@PROGRAM@" will be exchanged by "FDLog V1.xx", where xx is the current version of FDLog. Action-Templates (A): A certain action will be taken when converting the template. Some of these templates need a parameter which appears after a ":" after the template-name. The action will then be performed on the parameter _AFTER_ this ":". This parameter may also contain templates, but these templates must not be between two "@" but between two "%". I.e. @INCLUDE:%FULLUSERLOGNAME%@: with this the user's log of the current user will be included in the netmail. @FULLUSERLOGNAME@ is a macro-template that will be exchanged by the full name of the user's log of the current user. Logic-Templates (L): This template can either be true or false. If it is false, the rest of the current line will be ignored, if it is true, the rest of the line will be processed. In you invert a Logic-template by write a "!" before the template-keyword. I.e. @MOREAKAS@: If the current user used more than one AKA, the rest of the line will be processed, otherwise it will be ignored. I.e. "!MOREAKAS@: If the current user only used one AKA, the rest of the line will be processed, otherwise it will be ignored. ────────────────────────────────────────────────────────────────────────────── 5.3 Line-Feeds in templates ────────────────────────────────────────────────────────────────────────────── Usually after every line in a template file a line-feed will be added to the compiled text. These line-feeds can be supressed if there is "\" at the end of the line. There will also be no line-feed if a Template-Line gets converted ══════════════════════════════════════════════════════════════════════════════ Template-Types, Line-Feeds Page 39 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── to nothing, i.e. because a Logic-Template at the line-beginning was false. If you want to add a line-feed without any text after a Logic-Template, write ONE space after this Logic-Template, which is located at the begin of a new line. There are some samples in the included ENGLISH.TPL. ────────────────────────────────────────────────────────────────────────────── 5.4 Template-Formating ────────────────────────────────────────────────────────────────────────────── It is possible to format the result of Macro- or Action-Template. The format- command is located directly after the starting @ and written within brackets. There are format commands with one, two or three identifiers. These ident- ifiers are seperated either with ",", ":" or ";". You can user your favorite one ;-) The style of the format-command was taken from FileMgr (C) FileMgr Dev. Used with permission. * Format 1: (one identifier) <len> force length to be <len> @(6)PROGRAM@ 'FDLog ' @(15)USERLOGNAME@ 'LOTH0815.LOG ' format keyword in uppercase @(U)PROGRAM@ 'FDLOG V1.19' <L> format keyword in lowercase @(L)PROGRAM@ 'fdlog v1.19' format keyword in a proper way @(P)PROGRAM@ 'Fdlog V1.19' * Format 2: (two identifiers) <pos>,<len> start at position <pos> and force length to be <len> @(2,5)PROGRAM@ 'DLog ' @(2,15)USERLOGNAME@ 'OTH0815.LOG ' <R>,<len> justify to the right with forced length of <len> @(R,15)PROGRAM@ ' FDLog V1.19' @(R,15)USERLOGNAME@ ' LOTH0815.LOG' <C>,<len> center justification with forced length of <len> @(C,15)PROGRAM@ ' FDLog V1.19 ' @(C,15)USERLOGNAME@ ' LOTH0812.LOG ' ,<len> convert to uppercase with forced length of <len> ══════════════════════════════════════════════════════════════════════════════ Template-Formating Page 40 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── @(U,15)PROGRAM@ 'FDLOG V1.19 ' <L>,<len> convert to lowercase with forced length of <len> @(L,15)PROGRAM@ 'fdlog v1.19 ' ,<len> convert in a proper way with forced length of <len> @(P,15)PROGRAM@ 'Fdlog V1.19 ' * Format 3: (three identifiers) <pos>,<len>,<char> start at position <pos>, force <len> length and fill with char. @(3,15,-)PROGRAM@ 'log V1.19------' @(1,15,*)USERLOGNAME@ 'LOTH0815.LOG***' <R>,<len>,<char> right justification, length <len>, fill with <char> @(R,15,-)PROGRAM@ '----FDLog V1.19' @(R,15,*)USERLOGNAME@ '***LOTH0815.LOG' <C>,<len>,<char> center justification, forced length <len>, fill with <char> @(C,15,-)PROGRAM@ '--FDLog V1.19--' @(C,15,*)USERLOGNAME@ '*LOTH0815.LOG**' ,<len>,<char> convert to uppercase, forced length <len>, fill with <char> @(U,15;!)PROGRAM@ 'FDLOG V1.19!!!!' <L>;<len>;<char> convert to lowercase, forced length <len>, fill with <char> @(L,15,.)PROGRAM@ 'fdlog v1.19....' ,<len>,<char> convert in a proper way, forced length <len>, fill with <char> @(P;15;?)PROGRAM@ 'Fdlog V1.19????' ────────────────────────────────────────────────────────────────────────────── 5.5 Available Templates ────────────────────────────────────────────────────────────────────────────── This is a list of all available templates in FDLog. The templates are appear sorted alphabetically. All templates always refer to the system which the netmail is written to. Template-keyword: Type: Description: ----------------- ----- ----------------------------------------------------- ADDRESS A Address of current system. ══════════════════════════════════════════════════════════════════════════════ Available Templates Page 41 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── AKALIST A Main-AKAs used of current system. AMPM[:Time] A/M Display "am" or "pm" depending on current time. If :Time is used am/pm of this time-string will be displayed. APR:<String> A Define name for April AUG:<String> A Define name for August COMMENT L This template is always false, you can use it for comments in the template file. CONNTIME L ConnTime in FDLog.INI CRASH A Set status Crash on this message. CURRENCY M Curreny D3[:Date] A/M Current Dayname (3 Chars). If :Date is used the dayname of this date will be displayed. DAY[:Date] A/M Current Dayname. If :Date is used the dayname of this date will be displayed. DD[:Date] A/M Current Day. If :Date is used the Day of this date will be displayed. DEC:<String> A Define name for December DELETESENT A Set status Del/Sent on this message. This is only valid if you used FATTACH:<file> before. ENDDATE M Analyze-Enddate on current FDLog-Run. ERRORLOGNAME M Name of FDLog's error logfile. EXT M Current file-extension FATTACH:<file> A Attach file <file> to this message. FEB:<String> A Define String for February FIRSTCALLDATE M Date of first call to/from current system. FIRSTCALLTIME M Time of first call to/from current system. FRI:<String> A Define name for Friday FULLUSERLOGNAME M Full name of user's log of current system. HIGHCOST L HighCost in FDLog.INI HOLD A Set status Hold on this message. HOUR12[:Time] A/M Current Hour in 12 Hour format. If :Time is used, the Hour of this Time-String will be converted into 12-Hour format. HOUR[:Time] A/M Current Hour. If :Time is used, the Hour of this time will be displayed. INCALLS M Number of inbound calls. INCOST M Total cost of inbound calls. INCLUDE:<File> A Include <file> into netmail. <file> may have templates in it. INEXPCOST M Total extra cost caused by inbound calls during high-cost periods. INEXPCOSTPERC M Percent of extra cost in comparison to total cost. INEXPTIME M Inbound-Time in highcost-periods from current system. INEXPTIMEPERC M Percent of highcost-inbound time in comparison to total-inbound time. INFRCVD M kB/MB Echofiles received in inbound calls from current system. INFRCVDPERC M Percent of received EchoFiles in comparison to total received. INFREQED L Inbound-filerequests appeared? INFREQLIST M List of file-requests in inbound calls. INFREQS M Number of file-requests in inbound calls. INFSENT M kB/MB Echofiles sent in inbound calls from current system. INFSENTPERC M Percent of sent EchoMail in comparison to total sent. ══════════════════════════════════════════════════════════════════════════════ Available Templates Page 42 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── INFTRANS M Total inbound EchoFile transfer (kB/MB). INFTRANSPERC M Percent of transferred EchoFiles in comparison to total transfer. INHANDCOST M Total inbound handshaking cost. INHANDCOSTPERC M Percent of handshaking cost in comparsion to total inbound cost. INHANDTIME M Total inbound handshaking time. INHANDTIMEPERC M Percent of handshaking time in comparison to total connect time. INLOWCOST M Total cost of inbound calls if there were only calls during low-cost periods. INLOWCOSTPERC M Percent of only low-cost calls in comparison to total cost. INLOWTIME M Inbound-Time in lowcost-periods to current system. INLOWTIMEPERC M Percent of lowcost-inbound time in comparison to total-inbound time. INMRCVD M kB/MB Mail received in inbound calls from current system. INMRCVDPERC M Percent of received mail in comparison to total received. INMSENT M kB/MB Mail sent in inbound calls from current system. INMSENTPERC M Percent of sent mail in comparison to total sent. INMTRANS M Total inbound mail transfer (kB/MB). INMTRANSPERC M Percent of transferred mail in comparison to total transfer. INRCVD M kB/MB received in inbound calls from current system. INSENT M kB/MB sent in inbound calls from current system. INTRANS M Total inbound transfer (kB/MB). INTIME M Inbound-Time from current system JAN:<String> A Define name for January JUL:<String> A Define name for July JUN:<String> A Define name for June LASTCALLDATE M Last call date from/to current system LASTCALLTIME M Last call time from/to current system LINES M Number of system-lines. M3[:Date] A/M Current Monthname (3 Chars). If :Date is used the monthname of this date will be displayed. MAR:<String> A Define name for March MAY:<String> A Define name for May MIN[:Time] A/M Current Minute. If :Time is used, the Minute of this time will be displayed. MM[:Date] A/M Current Month. If :Date is used the Month of this date will be displayed. MON:<String> A Define name for Monday MOREAKAS L Current system used more than one AKA. MONTH[:Date] A/M Current Monthname. If :Date is used the monthname of this date will be displayed. MONTHLYREP L Is FDLog's current run a monthly-run? MULTILINE L Is your system a multiline-system? MYAKA M AKA used for sending this netmail. NET:<Addr> A Net of address. NODE:<Addr> A Node of address. NOKILL A Don't set kill status on this message. NOV:<String> A Define name for November OCT:<String> A Define name for October ONECALL L User only has only one call ══════════════════════════════════════════════════════════════════════════════ Available Templates Page 43 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── OUTCALLS M Number of outbound calls. OUTCOST M Total cost of outbound calls. OUTEXPCOST M Total extra cost caused by outbound calls during high-cost periods. OUTEXPCOSTPERC M Percent of extra cost in comparison to total cost. OUTEXPTIME M Outbound-Time in highcost-periods to current system. OUTEXPTIMEPERC M Percent of highcost-outbound time in comparison to total-outbound time. OUTFRCVD M kB/MB Echofiles received in outbound calls to current system. OUTFRCVDPERC M Percent of received EchoFiles in comparison to total received. OUTFREQED L Outbound-filerequests appeared? OUTFREQLIST M List of file-requests in outbound calls. OUTFREQS M Number of file-requests in outbound calls. OUTFSENT M kB/MB Echofiles sent in outbound calls to current system. OUTFSENTPERC M Percent of sent EchoMail in comparison to total sent. OUTFTRANS M Total outbound EchoFile transfer (kB/MB). OUTFTRANSPERC M Percent of transferred EchoFiles in comparison to total transfer. OUTHANDCOST M Total outbound handshaking cost. OUTHANDCOSTPERC M Percent of handshaking cost in comparsion to total outbound cost. OUTHANDTIME M Total outbound handshaking time. OUTHANDTIMEPERC M Percent of handshaking time in comparison to total connect time. OUTLOWCOST M Total cost of outbound calls if there were only calls during low-cost periods. OUTLOWCOSTPERC M Percent of only low-cost calls in comparison to total cost. OUTLOWTIME M Outbound-Time in lowcost-periods to current system. OUTLOWTIMEPERC M Percent of lowcost-outbound time in comparison to total-outbound time. OUTMRCVD M kB/MB Mail received in outbound calls to current system. OUTMRCVDPERC M Percent of received mail in comparison to total received. OUTMSENT M kB/MB Mail sent in outbound calls to current system. OUTMSENTPERC M Percent of sent mail in comparison to total sent. OUTMTRANS M Total outbound mail transfer (kB/MB). OUTMTRANSPERC M Percent of transferred mail in comparison to total transfer. OUTRCVD M kB/MB received in outbound calls to current system. OUTSENT M kB/MB sent in outbound calls to current system. OUTTRANS M Total outbound transfer (kB/MB). OUTTIME M Outbound-Time to current system POINT:<Addr> A Point of address. PROGRAM M FDLog with Versionnumber and "+", if registered. PROGRAMDATE M Compile date of this FDLog version. PROGRAMTIME M Compile time of this FDLog version. REALDURATION L RealDuration in FDLog.INI REQUESTABLE L Requestable in FDLog.INI SAT:<String> A Define name for Saturday SEC[:Time] A/M Current Second. If :Time is used, the Second of this time will be displayed. ══════════════════════════════════════════════════════════════════════════════ Available Templates Page 44 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── SCHEDINFO M Info-String from FDLog's internal Scheduler (for periodic-logs, i.e. March 1995) SEP:<String> A Define name for September SHORTTPLNAME M Name of current template, without path and extension. SOURCENAME:<Name> A Name of Sender of netmail. STARTDATE M Analyze-Startdate on current FDLog-Run. SUBJECT:<Subject> A Subject of netmail SUN:<String> A Define name for Sunday SYSOPFIRSTNAME M Firstname of current SysOp. SYSOPLASTNAME M Lastname of current SysOp. SYSOPNAME M Name of current SysOp. SYSTEMNAME M The name of your system. THU:<String> A Define name for thursday TRXADDRESS M Address of time-server TRXDATE M Date of failed Tranx-Session TRXDIFFMINS M Time difference in minutes TRXDIFFSECS M Time difference in seconds TRXFIRSTNAME M First name of time-server Sysop TRXLASTNAME M Last name of time-server Sysop TRXLOGNAME M Name of used mailer-logfile TRXMAXDIFF M Max. allowed time difference in minutes TRXNAME M Sysop of time-server TRXOWNDATE M Own date (normal) from Tranx-line TRXOWMTIME M Own time (normal) from Tranx-line TRXOWNUNIX M Own unix date (Hex) from Tranx-line TRXREMDATE M Remote date (normal) from Tranx-line TRXREMTIME M Remote time (normal) from Tranx-line TRXREMUNIX M Remote unix date (Hex) from Tranx-line TRXTIME M Time of failed Tranx-Session TOTCALLS M Number of in/outbound calls. TOTCOST M Total cost of in/outbound calls. TOTEXPCOST M Total extra cost caused by in/outbound calls during high-cost periods. TOTEXPCOSTPERC M Percent of extra cost in comparison to total in/outbound cost. TOTEXPTIME M In/outbound-time in highcost-periods to/from current system. TOTEXPTIMEPERC M Percent of highcost-in/outbound time in comparison to total in/outbound time. TOTFRCVD M kB/MB Echofiles received in in/outbound calls to/from current system. TOTFRCVDPERC M Percent of received EchoFiles in comparison to total in/outbound received. TOTFSENT M kB/MB Echofiles sent in in/outbound calls to/from current system. TOTFSENTPERC M Percent of sent EchoMail in comparison to total in/outbound sent. TOTFTRANS M Total in/outbound EchoFile transfer (kB/MB). TOTFTRANSPERC M Percent of transferred EchoFiles in comparison to total in/outbound transfer. TOTHANDCOST M Total in/outbound handshaking cost. TOTHANDCOSTPERC M Percent of handshaking cost in comparsion to total in/outbound cost. TOTHANDTIME M Total in/outbound handshaking time. TOTHANDTIMEPERC M Percent of handshaking time in comparison to total in/outbound connect time. ══════════════════════════════════════════════════════════════════════════════ Available Templates Page 45 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── TOTLOWCOST M Total cost of in/outbound calls if there were only calls during low-cost periods. TOTLOWCOSTPERC M Percent of only low-cost calls in comparison to total in/outbound cost. TOTLOWTIME M In/outbound-Time in lowcost-periods to/from current system. TOTLOWTIMEPERC M Percent of lowcost-in/outbound time in comparison to total in/outbound time. TOTMRCVD M kB/MB Mail received in in/outbound calls to/from current system. TOTMRCVDPERC M Percent of received mail in comparison to total in/outbound received. TOTMSENT M kB/MB Mail sent in in/outbound calls to/from current system. TOTMSENTPERC M Percent of sent mail in comparison to total in/outbound sent. TOTMTRANS M Total in/outbound mail transfer (kB/MB). TOTMTRANSPERC M Percent of transferred mail in comparison to total in/outbound transfer. TOTRCVD M kB/MB received in in/outbound calls to/from current system. TOTSENT M kB/MB sent in in/outbound calls to/from current system. TOTTRANS M Total in/outbound transfer (kB/MB). TOTTIME M In/outbound-Time to current system TPLLINE M Linenumber in current template-file. TPLNAME M Name of current template, with path and extension. TRUNCSENT A Set status Trunc/Sent on this message. This is only valid if you used FATTACH:<file> before. TUE:<String> A Define name for Tuesday USEREMOTECOST L UseRemoteCost in FDLog.INI USERFIRSTNAME M Firstname of FDLog-User, if registered. USERLASTNAME M Lastname of FDLog-user, if registered. USERLOGNAME M Name of current userlog with extension, but without path. USERNAME M Name of FDLog-User, if registered. WED:<String> A Define name for Wednesday Y4[:Date] A/M Current Year (incl. century). If :Date is used the Year of this date will be displayed. YEARLYREP L Is FDLog's current run a yearly-run? YY[:Date] A/M Current Year. If :Date is used the Year of this date will be displayed. ZONE:<Addr> A Zone of address. Note: ----- :Time always has the Format hh:mm:ss (i.e. 14:56:12) :Date always has the Format DD-MMM-YY (i.e. 4-Mar-95) 198 templates available. ────────────────────────────────────────────────────────────────────────────── 6. Updates ────────────────────────────────────────────────────────────────────────────── FDLog is ONLY distributed via Electronic Bulletin Board Systems (BBS). You can ══════════════════════════════════════════════════════════════════════════════ Updates Page 46 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── always find the latest public version on my BBS: Taurus Alpha 1: +43-732-611243 V34 (FIDONet 2:314/20) +43-732-609032 ZyX 19k2 (FIDONet 2:314/21) +43-732-663090 ZyX 19k2 (FIDONet 2:314/22) +43-732-651056 ISDN X75 & CCB (FIDONet 2:314/23) I release new public versions of FDLog when I think it's time to release them. Further I release Beta-Versions with the latest improvements and bug fixes. These Beta-Versions are only working with a proper Registration Key. This gives YOU, the registered FDLog user a faster access to the latest updates of FDLog. I have installed the following Magics for FIDO-filerequests: FDLOG : Latest FDLog Public release FDL_BETA: Latest FDLog Beta release, only for registered users FDL_DEMO: Obtain a personal Demo-Key for FDLog that gives you access to all the powerful features of FDLog and the current Beta-Version for five weeks! Get it >>NOW<<! You can get this Demo-Key also via netmail, if you do not want to call my system directly. Just write a netmail like this and you will get an UUENCODED demo-key for FDLog: By: Bugs Bunny, Bugsy (2:222/222) To: Keyserver, Taurus Alpha 1 #1 V34 (2:314/20) Re: I gonna check it out St: Pvt Loc Kill/Sent -------------------------------------------------------------------- %FDL_DEMO --- Additionally to this I have installed two fileechos: FDLOG : FDLog Public Release Hatch echo FDL_BETA: FDLog Beta Release Hatch echo These fileechos should be available at >> Interface << Filebone, 2:281/506 VFC, V34 & ISDN Taurus Alpha 1 , 2:314/20 V34, VFC, ZyX 19k2 & ISDN Mustang BBS , 2:2490/2001 HST, ZyX 19k2, V34, VFC & ISDN Infocom BBS , 2:2490/2010 VFC & ISDN The frequency of updates depends on the time I have to work on FDLog and if there is something to work on. If there is a bug somewhere you can be quite sure that it will be fixed as soon as possible. FDLog is not the kind of software that can be completed. Lots of future versions will come - there will be a lots of new functions; there are really enough ideas ;-) ══════════════════════════════════════════════════════════════════════════════ Updates Page 47 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── ────────────────────────────────────────────────────────────────────────────── 7. Bug reports ────────────────────────────────────────────────────────────────────────────── If you have found a bug in FDLog please be so free to tell me about it. I will try to fix it as soon as possible. When reporting a bug (the best way will be via NM) please write down the version you used when the error occured. If FDLog quits with a runtime error, please send the created FDLOG.ERR to me as well. Please ALWAYS send the .INI file and your mailer's log file you used to me. Otherwise it could be difficult for me to reproduce the malfunction. ────────────────────────────────────────────────────────────────────────────── 7.1 Known Bugs ────────────────────────────────────────────────────────────────────────────── Currently none from my side, but I am sure FDLog is not 100% bugfree, as no program can be 100% bugfree :-) However, I encountered that the runtime-system can cause problems with the virtual memory (VM) management under special circumstances. In this case, FDLog gets terminated without control of my error-handler and therefore the file FDLOG.LOC remains in FDLog's path. This does not cause any problems in this version of FDLog. Please note, that FDLog has not completed its work at this point and not all data has been processed! A loss of data cannot occur. If this problem permanently occurs on your system please check and "play" with the setup of yout EMS-Handler (EMM386, QEMM). I had the problem lately together with QEMM 7.04 in Stealth mode with partial DOS-Up. Enabling Full DOS-Up has removed the problem so far. The error-message of FDLog at my system was "VM integrity failure", at another system running QEMM 7.5 a GPF was reported by QEMM. ────────────────────────────────────────────────────────────────────────────── 8. Suggestions ────────────────────────────────────────────────────────────────────────────── If you have any suggestions for FDLog to make it even better please feel free to tell me about it - just write a netmail to me. Thanks. ────────────────────────────────────────────────────────────────────────────── 9. Thanks ────────────────────────────────────────────────────────────────────────────── I'd like to thank serveral people for their help and their ideas. Without them FDLog would not be so versatile and powerful as it is now. Special thanks to (in alphabetical order): Josef Braun (Austria) Guenther Faulhuber (Austria) Walter Hilgaertner (Austria) Ron Huiskes (Holland) Gero Dirk Lachner (Germany) Alex Palisek (Austria) Markus Schebsdat (Germany) Sascha Vogt (Austria) ══════════════════════════════════════════════════════════════════════════════ Bug reports, Known Bugs, Suggestions, Thanks Page 48 User's manual for FDLog V1.22 (C) 1994,96 by Lothar Lindinger ────────────────────────────────────────────────────────────────────────────── Michael Wilson (Great Britain) Also thanks to Peter Eigner how showed me how FDLog did not work at his "funny" system. I spent some hours to make it working and fixed some bugs right there. A big thanks also to all others who have already registered FDLog. Due to neverending interventions of Johannes Philipp "Phill" Krone the highcost-feature is now even available for unregistered users.... ;-) Thanks to Matthias Tichy for his freeware netmail-processing software MailMan. Though I needed some bugfixes it's just working great now :-) Frequest MMBETA, MMBETAX (DOS/DMPI) or MMBETAP (OS/2) at my system for the latest version of MailMan. ────────────────────────────────────────────────────────────────────────────── 10. Trademarks, Copyrights ────────────────────────────────────────────────────────────────────────────── Product | Holder -------------+------------------------------------ DocForma | Lothar Lindinger EasyERP | Kai-Jens Meyer, Stefan Briesenick | und René Kreisbeck FDLog | Lothar Lindinger FileMgr | Ron Huiskes for FileMgr Dev. FIPS | Oliver Weindl & Johann Weinzierl FrontDoor | Joaquim H. Homrighausen InterMail | InterMail Sales, Inc. MailMan | Matthias Tichy (TSP) McMail | Albert Freriks & Gordian Schuermann MS-DOS | Microsoft Corp. OS/2 | IBM Corp. RP | Hans Siemons for Prime Productions | together with Marco Miltenburg SuperBBS | Risto Virkkala & Aki Antman T-Mail | Andy Elkin Windows | Microsoft Corp. Xenia | Arjen G. Lentz This document was completely formatted with DocForma. ══════════════════════════════════════════════════════════════════════════════ Trademarks, Copyrights Page 49